Altinity / Altinity/clickhouse-operator
Support custom labels on Pods created by clickhouseinstallations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Description
When deploying a ClickHouseInstallation, there does not appear to be a supported way to add custom labels to the Pods created by the operator.
We would like to apply custom organizational labels to all ClickhousePods generated by a ClickHouseInstallation, without relying on external mutating admission controllers or post-deployment patches.
For example:
metadata:
labels:
xxx: yyy
or
spec:
templates:
podTemplates:
podLabels:
xxx: yyy
which would then be propagated to the Pod templates of the generated StatefulSets.
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 at the ClickHouseInstallation podTemplates and podLabels configuration described in the issue, then trace how generated ClickHousePods become StatefulSet pod templates. Define the supported label location and verify that labels propagate to every generated Pod. Add or update coverage for the configuration and run the operator's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100