-
Notifications
You must be signed in to change notification settings - Fork 113
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
Reconcile ScanSettingBindings when a TailoredProfile changes #792
Conversation
In case a TailoredProfile was valid, but then modified to be invalid, the configMap is still around. This is at best confusing and maybe even dangerous as existing scans will just happily carry on using that CM. Let's remove the configMap when the tailoredProfile is marked as invalid. Related: #791
/retest |
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 the code looks good! Let's wait and see if e2e test passes
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhrozek, Vincent056 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 |
Modifies the ScanSettingBinding controller to also watch for TailoredProfile CRs which link to a TP. This allows to reconcile ScanSettingBindings in case a TailoredProfile is modified, typically after fixing issues in a TailoredProfile without having to recreate the TailoredProfile. Fixes: #791
/retest |
@jhrozek: 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. |
/lgtm |
Modifies the ScanSettingBinding controller to also watch for
TailoredProfile CRs which link to a TP. This allows to reconcile
ScanSettingBindings in case a TailoredProfile is modified, typically
after fixing issues in a TailoredProfile without having to recreate the
TailoredProfile.
Fixes: #791
NOTE: I haven't had the chance to test the e2e addition at all. Feedback is welcome
in the meantime and maybe the tests will even pass :-)