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
Bug 1986090: Do not recreate CA deployment when CA CR is being deleted #215
Bug 1986090: Do not recreate CA deployment when CA CR is being deleted #215
Conversation
@JoelSpeed: This pull request references Bugzilla bug 1986090, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
@JoelSpeed: This pull request references Bugzilla bug 1986090, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
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 looks like a good solution, just curious if we could add a unit test to check the deletion time stamp part of this?
Reasonable request! I did have a look and our unit tests right now are a bit not great in this area, so it won't be trivial to add a test for this. I will look into adding a unit test for this tomorrow though. |
sounds good, i was hoping we could slip this into the reconcile test but maybe that was optimistic of me ;) |
27bf4c4
to
cd827b1
Compare
/test e2e-upgrade |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-demichev 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 |
/lgtm |
/override ci/prow/e2e-aws-operator The tests are broken, I've manually verified this, once this merged we can get the rest of the tests fixed |
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-operator 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. |
@JoelSpeed: All pull requests linked via external trackers have merged: Bugzilla bug 1986090 has been moved to the MODIFIED state. 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. |
/cherry-pick release-4.8 |
@JoelSpeed: new pull request created: #217 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. |
This is breaking our tests which use foreground deletion. The CAO fights the GC to delete and recreate the deployment, ensuring that the CA CR never goes away.
I have manually verified that this fixes the broken cluster autoscaler tests we are currently seeing in CI.