-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
daemon/cmd: improve stale cilium endpoint error handling. #22600
daemon/cmd: improve stale cilium endpoint error handling. #22600
Conversation
Going to convert this to a draft/CI debugging PR for the time being. The frequency of these errors in CI is concerning. |
/test-1.16-4.9 |
/test |
/test-1.16-4.9 |
2 similar comments
/test-1.16-4.9 |
/test-1.16-4.9 |
/test |
1 similar comment
/test |
/test-1.16-4.9 |
/test-1.24-5.4 |
/test-1.25-4.19 |
/test-1.26-net-next |
/test |
/test-1.16-4.9 |
/test-1.16-4.9 |
/test |
/test |
@tommyp1ckles This file doesn't exist in <= v1.12. Removing the needs-backport/* labels for those changes for now. |
Avoid error logging on no-op cleanup situations to avoid breaking CI.
Previously, if stale CEP cleanup was attempted and the CiliumEndpoint was already gone it would log an error.
This would go on to fail CI, on tests enforcing zero error logs.
In the case where the error is a
k8serrors.NotFound
, we don't need to consider this an error. This change differentiates between the two cases and logs info if its the no-op case.Signed-off-by: Tom Hadlaw tom.hadlaw@isovalent.com