-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CM-61: Rebase cert-manager v1.11 #113
Conversation
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
in v1.11 controller manifest: "--acme-http01-solver-image=", "--max-concurrent-challenges=" Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test e2e-operator |
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -3,36 +3,37 @@ module github.com/openshift/cert-manager-operator | |||
go 1.19 | |||
|
|||
require ( | |||
github.com/cert-manager/cert-manager v1.10.2 | |||
github.com/cert-manager/cert-manager v1.11.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should be consuming our downstream fork here, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took a note of this during last rebase, but probably left it untouched as we've been doing it this way since before. Assuming we push the exact same commits to our fork does it really matter. However, if you suggest adding it we can, probably just a matter of another replace(...)
block you're mentioning of right?
/assign |
bundle/manifests/cert-manager-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh Can you update the description to contains all the |
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@swghosh: This pull request references CM-61 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@thejasn I've updated the PR description with all the relevant information. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: swghosh, thejasn The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Adding qe-approved based on pre-merge test results in channel https://redhat-internal.slack.com/archives/C045YMPKR3M/p1682073637235019?thread_ts=1681844002.801959&cid=C045YMPKR3M |
cc: @davemulford for px-approved |
/unhold |
/label docs-approved |
I don't see anything major in the upstream docs about upgrading to this version. |
@swghosh: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
[v1.11.0] Rebase Checklist:
Signed-off-by: Swarup Ghosh swghosh@redhat.com
cert-manager changelog
v1.11.0