Resources specification missing for initContainers in template 'deployment.yaml'
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
The template 'deployment.yaml' provides the possibility to specify resources for 'containers' as follows:
resources:
{{ toYaml .Values.resources | indent 10 }}
The resources specification is missing for the 'initContainers'.
That's why the deployment fails in my environment due to:
Error creating: pods "nextcloud-56946775f-28snp" is forbidden: failed quota: xxx-resourcequota-yyyy: must specify cpu,memory
I can create a default k8s LimitRange, but that is just a bad workaround.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the deployment.yaml template and compare the existing containers resource block with the initContainers section. Confirm how resource values are supplied for containers, then ensure the rendered deployment includes the required CPU and memory resources for initContainers. Done means the chart can satisfy a Kubernetes ResourceQuota without relying on a default LimitRange.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100