-
Notifications
You must be signed in to change notification settings - Fork 873
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(dashboard): Update pod status logic to support native sidecars. Fixes #3366 #3639
Conversation
Signed-off-by: Martyn Dale <mdale@verticalscope.com>
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3639 +/- ##
==========================================
+ Coverage 84.23% 84.34% +0.10%
==========================================
Files 154 154
Lines 18014 18021 +7
==========================================
+ Hits 15174 15199 +25
+ Misses 1996 1989 -7
+ Partials 844 833 -11 ☔ View full report in Codecov by Sentry. |
Go Published Test Results2 171 tests 2 171 ✅ 2m 54s ⏱️ Results for commit b4c79af. ♻️ This comment has been updated with latest results. |
E2E Tests Published Test Results 4 files 4 suites 3h 24m 0s ⏱️ For more details on these failures, see this check. Results for commit b4c79af. ♻️ This comment has been updated with latest results. |
Any news to make it not draft? |
I need a change to add tests as its failing the coverage checks. Theres no existing tests for any of this however to just extend which complicates it a little |
Nice, can't wait for support for native sidecars. Right now Argo Rollouts some sort of blocker for it |
Hi folks, any way to make this a priority? Seeing the same issue here. |
Ive still not got around to doing the tests but I've marked it as ready anyway in case the maintainers are willing to waive the requirement given the absence of testing for for all the functionality there in any form |
How can we get the maintainers involved? Seems like they are ignoring this issue. I posted a message in the argo-rollouts slack channel yesterday, and zero response. |
Facing the issue also. I manage to still use Argo (rollouts/cd) but the rollout status is not properly reported to ArgoCD, which seems to trigger a "bug" with some replicaset showing as ProgressDeadlineExceeded (#3457). The Issue seem to be "cosmetics" only (rollouts are properly promoted) but I'm wondering if some extra logic is being used during deployments, it may break. Big thanks to whoever will look into this :) |
Can you fix the lint issue by running |
Signed-off-by: Martyn Dale <mdale@verticalscope.com>
Hello, do you have sense when it will be released approximately? Asking because it becomes a major blocker to enable sidecars nowadays if you have in your stack Argo Rollouts. |
Published E2E Test Results 4 files 4 suites 3h 30m 58s ⏱️ For more details on these failures, see this check. Results for commit 3bd5f26. ♻️ This comment has been updated with latest results. |
Published Unit Test Results2 174 tests 2 174 ✅ 2m 54s ⏱️ Results for commit 3bd5f26. ♻️ This comment has been updated with latest results. |
Quality Gate passedIssues Measures |
Hello, @zachaller do you have sense when it will be released? |
Closes #3366
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.