Create option to pass namespace as an option to helm
- Dominant language
- Python
- Stars
- 37
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
helm has a flag -n, --namespace where the chart will be installed in the specified namespace. By specifying this as a CLI instead of inside the chart, you can create entire environments without a chart change. Use example
A DEV server where we want to create an environment for branch testing. We run the helm chart with the name of the branch and it can spin up a front end, back end, redis, DB, etc... Basically everything in a single namespace.
When no longer needed, delete the namespace.
Contributor guide
Research direction
Start by tracing how BitOps parses command-line options and invokes Helm. Use Helm's -n/--namespace behavior as the reference, then verify that a supplied namespace is used for the complete environment and that the documented cleanup workflow remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100