-
Notifications
You must be signed in to change notification settings - Fork 880
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
feat: add ability to verify canary weights before advancing steps #957
Conversation
16ca7e1
to
2d87c4a
Compare
97710a1
to
cfc0f8d
Compare
Codecov Report
@@ Coverage Diff @@
## master #957 +/- ##
==========================================
- Coverage 81.60% 81.33% -0.28%
==========================================
Files 99 100 +1
Lines 8732 8839 +107
==========================================
+ Hits 7126 7189 +63
- Misses 1151 1181 +30
- Partials 455 469 +14
Continue to review full report at Codecov.
|
Signed-off-by: Jesse Suen <[email protected]>
cfc0f8d
to
aca4d72
Compare
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
Signed-off-by: Jesse Suen <[email protected]>
e17d771
to
bfecdaa
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Resolves #701
This introduces an optional flag to the controller
--alb-verify-weight=true
. When enabled, for ALB ingresses, the controller will block a setWeight step until it is verified applied in the ALB target group listener rules. This requires that the controller has sufficient AWS privileges.Changes the TrafficRoutingReconciler interface from:
to
to support this.
Signed-off-by: Jesse Suen [email protected]