Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Why monocular-api have so much restarts ? #450
This happens pretty commonly for large chart repositories (e.g. the stable repository), it takes a while for Monocular to index it and Kubernetes will try to kill it. You can try increasing the charts' livenessProbe delay to prevent this from happening: https://github.com/kubernetes-helm/monocular/blob/master/deployment/monocular/values.yaml#L25
To make container response livenessProbe in time, I change foreground refresh to goroutine in main.go:
So when pod are starting at first time, it will start livenessProbe REST service in time then will not be killed by k8s.
And I also find lots of OOM issue:
To fix this, increase Pods spec:
Still didn't know why it exhaust so many memory. Maybe we can decrease parallel download semaphore? @prydonius Currently it is 15.