-
Notifications
You must be signed in to change notification settings - Fork 781
Rework selector labels #1830
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
base: main
Are you sure you want to change the base?
Rework selector labels #1830
Conversation
eb3b823 to
fc1ffcf
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1830 +/- ##
===========================================
- Coverage 39.44% 28.55% -10.89%
===========================================
Files 287 287
Lines 22706 22827 +121
===========================================
- Hits 8956 6518 -2438
- Misses 12777 15579 +2802
+ Partials 973 730 -243 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
0fab806 to
223bcdb
Compare
Addresses fluxcd#1312, fluxcd#1257, fluxcd#1115 Retains all `matchLabels` in the primary `Deployment` or `DaemonSet`, instead of picking the first one that matches the `-selector-labels`. Recreates the primary `Deployment` or `DaemonSet` if the `matchLabels` of the existing object are not equal. This must be done since `matchLabels` is an immutable field. The recreate happens before promoting the canary to primary (i.e. no traffic is being routed to the primary). Still appends `-primary` to the value of the first label that matches `-selector-labels`. This ensures that the canary and primary have a unique set of selector labels. `Service` selector also uses the full set of `matchLabels` and overrides the value of the first matching `-selector-labels` to route to canary or primary. Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Tests the `matchLabels` behavior for `Deployment`, `DaemonSet`, and `Service` Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
Signed-off-by: Kevin Snyder <[email protected]>
223bcdb to
24ffc5b
Compare
aryan9600
left a comment
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.
thank you for working on this. i do agree that the current behaviour is limiting. but since this'd be a breaking change, i think we should gate this behaviour behind a flag (something like --copy-all-selector-labels which is set to false by default.
Addresses #1312, #1257, #1115
Retains all
matchLabelsin the primaryDeploymentorDaemonSet, instead of picking the first one that matches the-selector-labels.Still appends
-primaryto the value of the first label that matches-selector-labels. This ensures that the canary and primary have a unique set of selector labels.Serviceselector also uses the full set ofmatchLabelsand overrides the value of the first matching-selector-labelsto route to canary or primary.Does not recreate the primary
DeploymentorDaemonSetif thematchLabelsof the existing object are not equal.Does update the
Serviceselector labels to match the new behavior.