Altinity / Altinity/clickhouse-operator
How to set dynamic parameter to .spec.configuration.files
Open
Nobody has claimed this yet.
stale
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
HI:
I want to create custom macros ,like this:
configuration:
files:
conf.d/customer_marco.xml: |
<yandex>
<macros>
<installation2>{chi}</installation2>
<cluster>demo</cluster>
<shard>{shard}</shard>
<replica>{replica}-{shard}</replica>
</macros>
</yandex>
and want get shardname 、replicaname、podname to set its,but it is not effect
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 issue's YAML example and the .spec.configuration.files setting, then review how the ClickHouse operator handles custom macros and values such as shard, replica, and pod names. Reproduce the configuration to determine whether these dynamic parameters are supported or why they have no effect; done means identifying the supported behavior and documenting or reporting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100