-
Notifications
You must be signed in to change notification settings - Fork 743
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
Adjusted Nginx ingress canary headers on init and promotion #907
Conversation
Signed-off-by: Iaroslav Vorozhko <[email protected]>
Signed-off-by: Iaroslav Vorozhko <[email protected]>
9ee487f
to
41481c1
Compare
Codecov Report
@@ Coverage Diff @@
## main #907 +/- ##
==========================================
+ Coverage 56.76% 56.95% +0.18%
==========================================
Files 69 69
Lines 5704 5710 +6
==========================================
+ Hits 3238 3252 +14
+ Misses 1983 1975 -8
Partials 483 483
Continue to review full report at Codecov.
|
@vorozhko can you please enable the webhook in NGINX e2e tests to verify that this works? Thanks |
Default ingress nginx helm has webhook enabled by default. |
So how come the test passes without this PR? Maybe the version we use in e2e doesn’t have the webhook? |
…ook after canary promotion Signed-off-by: Iaroslav Vorozhko <[email protected]>
ad4e53d
to
d7999e6
Compare
Added Nginx e2e tests to cover validation webhook case. |
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.
LGTM
Thanks @vorozhko 🏅
Thank you too! |
Adjusted canary headers after canary deployment is promoted
It resolves validation webhook issue