-
Notifications
You must be signed in to change notification settings - Fork 153
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
Avoid deleting KubeVirt Priority Class #670
Conversation
All tests passed |
/lgtm |
All tests passed |
2 similar comments
All tests passed |
All tests passed |
KV Priority Class is needed to start virt-operator but OLM is currently not able to create it so HCO is trying to create it ASAP. With #669 we are trying to create it as soon as HCO starts. But, for the same reason, we should not trying to delete it it when the user deletes HCO CR because virt-operator should continue running even if HCO CR got deleted. In the past we were trying to delete the priority class but we was failing on that just because we forgot to set app label on that and componentResourceRemoval is explictly checking for that before really deleting. Signed-off-by: Simone Tiraboschi <[email protected]>
All tests passed |
/test hco-e2e-aws |
@tiraboschi: The specified target(s) for
Use 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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa 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 |
Avoid deleting KubeVirt Priority Class
KV Priority Class is needed to start virt-operator
but OLM is currently not able to create it so HCO
is trying to create it ASAP.
With #669
we are trying to create it as soon as HCO starts.
But, for the same reason, we should not trying to
delete it it when the user deletes HCO CR because
virt-operator should continue running even if HCO
CR got deleted.
In the past we were trying to delete the priority
class but we was failing on that just because we forgot
to set app label on that and componentResourceRemoval is
explictly checking for that before really deleting.
Release note: