-
Notifications
You must be signed in to change notification settings - Fork 116
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
Fix namespace selector comparison for webhook #1985
Fix namespace selector comparison for webhook #1985
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1985 +/- ##
==========================================
- Coverage 49.32% 47.32% -2.01%
==========================================
Files 72 77 +5
Lines 7008 7352 +344
==========================================
+ Hits 3457 3479 +22
- Misses 3420 3742 +322
Partials 131 131 |
We should only compare supported labels and not everything on the namespace, otherwise we can end up being stuck in a `SPOD` with the `UPDATING` state. We now only compare supported webhook labels and use them as indicator if it requires and update or not. Fixes kubernetes-sigs#1981 Signed-off-by: Sascha Grunert <[email protected]>
68b7a91
to
d7f11ef
Compare
@kubernetes-sigs/security-profiles-operator-maintainers PTAL |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JAORMX, saschagrunert 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
We should only compare supported labels and not everything on the namespace, otherwise we can end up being stuck in a
SPOD
with theUPDATING
state. We now only compare supported webhook labels and use them as indicator if it requires and update or not.Which issue(s) this PR fixes:
Fixes #1981
Does this PR have test?
Yes
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?