Altinity / Altinity/clickhouse-operator
feature: templating for nodeSelector
Open
Nobody has claimed this yet.
feature
stale
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Ability to bind specific replicas/shards to k8s nodes without copy-paste whole podTemplate for each replica.
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/hostname
operator: In
values:
- hostname1
- key: replica_name
operator: In
values:
- {replicaID}
It useful in case of local path provisioning.
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
No file or test is named. Start by tracing the operator's podTemplate and nodeSelector handling, then review how replica and shard identities are available during scheduling. Done means users can bind specific replicas or shards to Kubernetes nodes through templating without copying a podTemplate for each one, including the local path provisioning case.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100