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

Possible monitor InitContainer with OOMHero? #12

Open
zanhsieh opened this issue Jan 11, 2023 · 2 comments
Open

Possible monitor InitContainer with OOMHero? #12

zanhsieh opened this issue Jan 11, 2023 · 2 comments

Comments

@zanhsieh
Copy link

zanhsieh commented Jan 11, 2023

Hello,

Thanks for such a great project.

Just curious if there is any example configuration for OOMHero to monitor initContainer OOMKilled case?

@ricardomaraschini
Copy link
Owner

Interesting question. I don't think you can as there is no way, as far as I know, of using sidecars for init containers. Init containers are meant to be something finite, I mean, more like a batch thing right ?

@zanhsieh
Copy link
Author

zanhsieh commented Jan 12, 2023

Thanks for swift feedback. Yes, they are finite, but one of cases I hit is cp was OOMKilled before the main container kicking in. After investigation, I guess it was InitContainer pulling some helm chart from OCI registry (e.g. Google Artifactory Registry), extracting it, and then perform helm template ... | kubectl apply -f .... The case happened mostly on high network latency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants