I would like to see the ability to specify requests/limits on the statefulset init container(s).
Is your feature request related to a problem? Please describe.
We have some restrictions in our cluster where all pods must define their requests and limits. We've had to introduce a LimitRange with default values just for this helm chart. I believe this option should be in the chart itself.
Describe the solution you'd like
In the values file, I would like to provide the following:
...
## Optional resource requests and limits for the CouchDB container
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
resources: {}
# requests:
# cpu: 100m
# memory: 128Mi
# limits:
# cpu: 56
# memory: 256Gi
## Optional resource requests and limits for the Initialization Container for CouchDB
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
initResources: {}
# requests:
# cpu: 100m
# memory: 128Mi
# limits:
# cpu: 56
# memory: 256Gi
...
Describe alternatives you've considered
There is no way to directly specify the resources that an initcontainer should consume. You have to create a LimitRange object similar to this:
Hey all,
I would like to see the ability to specify requests/limits on the statefulset init container(s).
Is your feature request related to a problem? Please describe. We have some restrictions in our cluster where all pods must define their requests and limits. We've had to introduce a LimitRange with default values just for this helm chart. I believe this option should be in the chart itself.
Describe the solution you'd like In the values file, I would like to provide the following:
Describe alternatives you've considered There is no way to directly specify the resources that an initcontainer should consume. You have to create a LimitRange object similar to this:
But this is now a namespace wide default