Skip to content
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

Closed
corang opened this issue Apr 16, 2024 · 5 comments
Closed

Neuvector updater pod sidecar never exits #347

corang opened this issue Apr 16, 2024 · 5 comments
Labels
possible-bug Something may not be working

Comments

@corang
Copy link
Contributor

corang commented Apr 16, 2024

Steps to reproduce

  1. Have neuvector running for any extended period of time

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

@corang corang added the possible-bug Something may not be working label Apr 16, 2024
@corang
Copy link
Contributor Author

corang commented Apr 16, 2024

As a workaround I've been portforwarding port 15000 from the sidecar and running curl -X POST http://localhost:15000/quitquitquit but this is obviously manual and shouldn't be necessary

@mjnagel
Copy link
Contributor

mjnagel commented Apr 17, 2024

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.

@mjnagel
Copy link
Contributor

mjnagel commented May 13, 2024

Linking defenseunicorns/pepr#745

@mjnagel
Copy link
Contributor

mjnagel commented May 24, 2024

Should be resolved by #419 - leaving open until that is released and we have feedback though.

@mjnagel mjnagel closed this as completed Jun 20, 2024
@mjnagel
Copy link
Contributor

mjnagel commented Jun 20, 2024

Tentatively closing - please reopen or create a new issue if you encounter this problem in latest core versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible-bug Something may not be working
Projects
None yet
Development

No branches or pull requests

2 participants