Altinity / Altinity/helm-charts
`operator.enabled` -> `operator.enable_if_not_found`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 57
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Hi! I have a problem with operator.enabled which seems to be requiring a value of true only if it is the first time installing the chart, because putting it to true while running helm down or helm upgrade seems to fail.
Changing this value after the first deployment is complicated for environments where builds are CI-automated, so I would like for this field to be automatically set to false if the operator is found for instance.
Does that make sense?
Contributor guide
No contributing guide indexed for this repository
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
Open charts/clickhouse/values.yaml at the referenced operator.enabled setting and read its surrounding comments. Trace where this value is consumed in the chart before deciding the scope. Done means the setting is renamed to operator.enable_if_not_found and avoids requiring manual changes after the operator is already present during installation, upgrade, or helm down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, helm, kubernetes
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100