Altinity / Altinity/clickhouse-operator
[Question] Is using PreviousTailAffinity in a single node cluster valid syntax?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Hey there. I tried to apply to following CR with podDistribution type set to PreviousTailAffinity and the reconciliation failed. I'm wondering if this is a semantic issue or a bug in operator. In case you want to see more details, I also attach the log of operator below.
Thanks.
apiVersion: clickhouse.altinity.com/v1
kind: ClickHouseInstallation
metadata:
name: test-cluster
spec:
configuration:
clusters:
- layout:
replicasCount: 2
shardsCount: 2
name: replicated
zookeeper:
nodes:
- host: zookeeper.zoo3.ns
defaults:
templates:
dataVolumeClaimTemplate: default
podTemplate: clickhouse:19.6
templates:
podTemplates:
- name: clickhouse:19.6
podDistribution:
- type: PreviousTailAffinity
spec:
containers:
- image: clickhouse/clickhouse-server:22.3
name: clickhouse-pod
volumeClaimTemplates:
- name: default
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 500Mi
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 with the supplied ClickHouseInstallation manifest and the attached affinity.log, then locate the operator's handling of PreviousTailAffinity and its validation rules. Reproduce the reconciliation failure with this manifest and determine whether the setting is valid for the shown cluster layout; done means the behavior is confirmed and documented or a clearly scoped operator bug is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100