-
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
fix: leaderelection uses the lock in the same ns as the controller #1717
Conversation
f10045c
to
f654a39
Compare
f654a39
to
a6d67dc
Compare
Codecov Report
@@ Coverage Diff @@
## master #1717 +/- ##
=======================================
Coverage 82.02% 82.02%
=======================================
Files 116 116
Lines 16096 16096
=======================================
Hits 13203 13203
Misses 2218 2218
Partials 675 675
Continue to review full report at Codecov.
|
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.
It looks like every e2e test all time out. I suspect the controller is not actually starting properly after this change for some reason.
- by default the lock is created in argo-rollouts - remove leader namespace from cli arguments Signed-off-by: Hui Kang <[email protected]>
a6d67dc
to
50af85c
Compare
Signed-off-by: Hui Kang <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Yeah, I think it is because the e2e cluster doesn't have the argo-rollouts` ns. Pushing a new commit to create the ns in e2e. |
@jessesuen , I think the failed tests are due to flakiness. |
Signed-off-by: Hui Kang [email protected]
close #1704
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.