-
Notifications
You must be signed in to change notification settings - Fork 18
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
Neuvector updater pod sidecar never exits #347
Comments
As a workaround I've been portforwarding port 15000 from the sidecar and running |
This is likely related to the pepr behavior you've seen with watches - pepr should be doing the sidecar termination (and has successfully in some long running environments from what I've seen). Good to track this issue, just want to call out that its likely coupled with watch problems - I would check if cycling the pepr watcher picks up those extra pods and terminates them. |
Linking defenseunicorns/pepr#745 |
Should be resolved by #419 - leaving open until that is released and we have feedback though. |
Tentatively closing - please reopen or create a new issue if you encounter this problem in latest core versions. |
Steps to reproduce
Expected result
Updater pod sidecars exit along with the main job
Actual Result
The main container exits and the sidecar runs forever
Visual Proof (screenshots, videos, text, etc)
Just manually cleared them I can grab a screenshot when it happens again
Severity/Priority
Low/med I think its mostly visual but I wonder if it affects neuvector's functionality
The text was updated successfully, but these errors were encountered: