Altinity / Altinity/clickhouse-operator

How to set dynamic parameter to .spec.configuration.files

Open
#1,318 4 comments 0 reactions 0 assignees View on GitHub

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.