-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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: Fix standalone pods and deployment health check pending. #7691
fix: Fix standalone pods and deployment health check pending. #7691
Conversation
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
Codecov Report
@@ Coverage Diff @@
## main #7691 +/- ##
==========================================
- Coverage 70.48% 66.60% -3.88%
==========================================
Files 515 587 +72
Lines 23150 28103 +4953
==========================================
+ Hits 16317 18719 +2402
- Misses 5776 8029 +2253
- Partials 1057 1355 +298
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
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!
nit: perhaps as a followup issues/PR we can add integration tests that can catch these cases where our standalone health checks are pending indefinitely? |
fixes: #7667
After some walkthrough, i feel its safe to remove empty namespace check. I added few tests added and realizes,
ConsolidateNamespaces
will never add an empty namespace to the return value if no new namespace are found.Here is the flow of how namespaces are updated in Deploy