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-190: Rebase v1.13 #143
CM-190: Rebase v1.13 #143
Conversation
@swghosh: This pull request references CM-189 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. 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. |
Skipping CI for Draft Pull Request. |
@swghosh: This pull request references CM-189 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. 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. |
/cc @thejasn @chiragkyal |
@swghosh: This pull request references CM-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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 all |
@swghosh: This pull request references CM-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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 all |
3313737
to
e441fe9
Compare
/cc @lunarwhite @xingxingxia |
@swghosh: This pull request references CM-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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 all |
787d537
to
c45b71d
Compare
bundle/manifests/cert-manager-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
* controller-runtime * controller-tools Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
* required bump to make bundle work without conflicts Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
* make update-with-container - pull upstream manifests * make update-bindata * make bundle -- this now uses kustomize v5, to fix some conflicts Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
* make bundle Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
…degen.sh Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
* make update-with-container * make update-bindata * make bundle Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
- make bundle Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
c45b71d
to
9e2fd90
Compare
/assign @thejasn |
@swghosh: This pull request references CM-190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.15.0" version, but no target version was set. 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: 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. |
bindata/cert-manager-deployment/controller/cert-manager-cluster-view-cr.yaml
Show resolved
Hide resolved
@@ -0,0 +1,12 @@ | |||
apiVersion: v1 |
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.
Whats the reason upstream for adding this?
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.
Seems like this is one of the new feature additions in cert-manager 1.13, cert-manager/cert-manager#5337 :)
cert-manager deployments would now rely upon a versioned config map implementation like revision controller in our library-go! 😮
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.
This will open up the operand for customisation https://github.com/AcidLeroy/cert-manager/blob/282a6d58a9038a9b54149b8f67fdc1a1a12560cc/deploy/charts/cert-manager/values.yaml#L122-L142 (which we don't want). Since we are ensuring CM exists via the static resource controller, I'm not sure if it also forces the CM to always be empty (hoping it does), Can you verify this?
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.
Our staticresourcecontroller doesn't update the resource, just creation and deletion based upon specific conditions. I can confirm this because I remember that in the past we used a method of adding annotations on a service account added by staticresourcecontroller and there was noticeably no reconciles to undo them. Going through implementation suggests likewise: https://github.com/openshift/library-go/blob/master/pkg/operator/staticresourcecontroller/static_resource_controller.go
However, IMO the user changing this config map manually would open the operand for customization and we don't have a good way to restrict that yet in our current changes.
bindata/cert-manager-deployment/webhook/cert-manager-webhook-deployment.yaml
Show resolved
Hide resolved
/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 |
[v1.13.0] Rebase Checklist:
Signed-off-by: Swarup Ghosh swghosh@redhat.com
cert-manager changelog
TODO