You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
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.
Hello,
Thanks for such a great project.
Just curious if there is any example configuration for OOMHero to monitor initContainer OOMKilled case?
The text was updated successfully, but these errors were encountered: