cloudfoundry / cloudfoundry/stratos
Stratos init pod's container is not classed as an init container
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Disclaimer... not sure what the difference between a container and an init-container is beside it's classification
- if possible need to switch the
config-initcontainer in ourstratos-config-init-xpod to be classed as a init container - this would provide a better 'state' for the pod (terminated completed is a good thing)
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 by locating the definition of the stratos-config-init-x pod and its config-init container in the repository. Check how the pod is created and represented, then verify that the container is declared as an init container and that a completed run gives the pod the expected terminated-completed state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100