-
Notifications
You must be signed in to change notification settings - Fork 3.4k
cilium-cli/connectivity: only check container restarts on v1.17+ #37823
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
cilium-cli/connectivity: only check container restarts on v1.17+ #37823
Conversation
f900d93 ("cilium-cli/connectivity: additionally check for container restarts") introduced a new check to the connectivity suite to validate that no Cilium-related pods have a container restart count greater than zero. However, this check is getting triggered way more than expected on older stable branches. Let's temporarily enable it only for Cilium v1.17 and later, while the discovered failures get investigated. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
/test |
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.
maybe open an issue so we don't forget to investigate the failures in future?
Pull Request is not mergeable
Opened #37870 to track the problem detected on v1.16. I didn't open one for the issue detected by the v1.15 CI as it was occurring on downgrade, and v1.14 is EOL. |
This reverts commit 6e80cf2. This version of the CLI still has the problem described in #37823 (comment) and is thus causing flakes in CI. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
This reverts commit 6e80cf2. This version of the CLI still has the problem described in #37823 (comment) and is thus causing flakes in CI. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
f900d93 ("cilium-cli/connectivity: additionally check for container restarts") introduced a new check to the connectivity suite to validate that no Cilium-related pods have a container restart count greater than zero. However, this check is getting triggered way more than expected on older stable branches. Let's temporarily enable it only for Cilium v1.17 and later, while the discovered failures get investigated.