-
Notifications
You must be signed in to change notification settings - Fork 719
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
elastic-internal-init-keystore initcontainer does not specify resources #2660
Comments
Sounds like a good idea. Let's do it! |
I investigated this one, we create init containers in a few different places: ElasticsearchFrom the
I think that 196MB of memory and 500m of CPU should be enough KibanaNode.JS is called behind the scene:
APM ServerKeystore entries are loaded with the Go binary
For both Kibana and APM Server invocations seems to be lightweight and use ~50 Mbytes of memory. I think we could set memory requirements to 128MB and 100m of CPU. |
Bug Report
What did you do?
Add a
secureSettings
secret to my elastic resourceThe init container
elastic-internal-init-keystore
was added to the statefulset but it was added with no resources.In a cluster with quotas enabled ( and no default limit range for cpu and memory ) this caused the roll restart of the statefulset to hang with
This works fine for the other initcontainer
elastic-internal-init-filesystem
which has values set for cpu and memory resourcesEnvironment
ECK version: 1.0.1
Kubernetes information:
Current WorkAround
Use a limitRange with default values for cpu and memory
The text was updated successfully, but these errors were encountered: