Altinity / Altinity/helm-charts
support adding environment variables in clickhouse chart
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 57
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Currently the chart doesn't support adding environment variable and I am assuming even AntiAffinity.
Currently I am using raw chart to apply. Yet, this helm will make it easier if it support user values instead of opinionated values
example
keeper:
podTemplates:
- name: default
spec:
containers:
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
Inspect the ClickHouse chart's values and templates around the keeper podTemplates configuration shown in the issue. Determine how user-provided container environment variables and pod anti-affinity should be represented, then verify that those values render into the generated Kubernetes manifests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100