adding resources to the defaultInitContainer
Open
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Our kubernetes environment has some restraints and therefore we need to set up resource definitions for every container that is started.
We are able to setup the resource definitions for the job container using:
"*":
default-cpus: .5
default-mem-mb: 512
cpu-request-ratio: .5
memory-request-ratio: .5
But we are using the defaultInitContainer from the values.yaml file which does not allow for setting up resource definitions.
Therefore the job will not start.
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 in values.yaml and trace how defaultInitContainer is configured and rendered for Kubernetes jobs. Make resource definitions configurable for that container, then verify that a job using defaultInitContainer starts with the requested resource settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100