[BUG] Multi-shard Clickhouse cluster configuration not rendered properly

[hunterlodge]

Describe the bug
When a multi-shard clickhouse cluster is created, each shard actually operates independently. I think this is due to the configuration file is not rendered properly with all shards included.

To Reproduce
Steps to reproduce the behavior:

1. set up a clickhouse cluster with more than one shard. My setup is as follows:

# k get cluster && kc get cmp && kc get instanceset && kc get pods
NAME            CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS    AGE
ch-v1-cluster                        Delete               Running   3d19h
NAME                      DEFINITION                           SERVICE-VERSION   STATUS    AGE
ch-v1-cluster-ch-keeper   clickhouse-keeper-24-1.0.0-alpha.1   22.9.4            Running   3d19h
ch-v1-cluster-shard-wv8   clickhouse-24-1.0.0-alpha.1          22.9.4            Running   3d19h
ch-v1-cluster-shard-z7b   clickhouse-24-1.0.0-alpha.1          22.9.4            Running   3d19h
NAME                      LEADER   READY   REPLICAS   AGE
ch-v1-cluster-ch-keeper            3       3          3d19h
ch-v1-cluster-shard-wv8            3       3          3d19h
ch-v1-cluster-shard-z7b            3       3          3d19h
NAME                        READY   STATUS    RESTARTS   AGE
ch-v1-cluster-ch-keeper-0   1/1     Running   0          3d19h
ch-v1-cluster-ch-keeper-1   1/1     Running   0          3d19h
ch-v1-cluster-ch-keeper-2   1/1     Running   0          3h19m
ch-v1-cluster-shard-wv8-0   1/1     Running   0          3d19h
ch-v1-cluster-shard-wv8-1   1/1     Running   0          3d19h
ch-v1-cluster-shard-wv8-2   1/1     Running   0          3h6m
ch-v1-cluster-shard-z7b-0   1/1     Running   0          3d19h
ch-v1-cluster-shard-z7b-1   1/1     Running   0          2d23h
ch-v1-cluster-shard-z7b-2   1/1     Running   0          3h5m

3. check the 00_default_overrides.xml under /etc/clickhouse-server/conf.d on a shard pod.

Expected behavior
This xml should have multiple sections of <shard> since each pod should be aware of its peers by this configuration file.

Screenshots

Additional context

• kubernetes: 1.30
• kubeblocks: v1.0.0.beta.21
• clickhouse serviceversion: 22.9.4
• clickhouse addon: https://github.com/apecloud/kubeblocks-addons/blob/main/addons/clickhouse/

[shanshanying]

@loomts PTAL