-
Notifications
You must be signed in to change notification settings - Fork 905
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: retain non-nginx canary annotations. Fixes: #1070 #3806
fix: retain non-nginx canary annotations. Fixes: #1070 #3806
Conversation
Signed-off-by: Jahvon Dockery <jdockery@cargurus.com>
5e58402
to
e7f029d
Compare
|
Published E2E Test Results 4 files 4 suites 3h 13m 39s ⏱️ Results for commit e7f029d. |
Published Unit Test Results2 265 tests 2 265 ✅ 2m 58s ⏱️ Results for commit e7f029d. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3806 +/- ##
==========================================
- Coverage 83.87% 83.83% -0.04%
==========================================
Files 162 162
Lines 18524 18531 +7
==========================================
- Hits 15537 15536 -1
- Misses 2119 2123 +4
- Partials 868 872 +4 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
hi @zachaller, i`m so glad this got merged! :) |
…roj#3806) fix: retain nginx canary annotations Signed-off-by: Jahvon Dockery <jdockery@cargurus.com>
The current patch applied for nginx canaries does not play nicely with other controller that may be modifying Ingress annotations. In our case, the Rancher
field.cattle.io/publicEndpoints
is repeatedly added/removed, resulting in a significant amount of updates to Ingress resources in the cluster.With this fix, before building and applying the canary ingress patch, all annotations from the existing canary ingress will be copied over to the desired Ingress.
fixes: #1070
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.