I've installed SigNoz using K8s Helm chart. My k8s...
# support
a
I've installed SigNoz using K8s Helm chart. My k8s cluster has custom domain name like instead of "cluster.local" it is "pbvl.custom.cluster". Now I am facing issues in clickhouse-operator. Inside clickhouse-operator it is searching for FQDN with "x.x.x.svc.cluster.local" instead of "x.x.x.svc.pbvl.custom.cluster". Anyone facing similar issues or have any insights about how can I resolve this issue? Thanks!
d
this seems like a way around it if the helm chart doesn't expose what clickhouse-operator uses... https://stackoverflow.com/questions/48326773/how-to-change-the-cluster-local-default-domain-on-kubernetes-1-9-deployed-with-k
n
Hey @Abid Hasan Muin, can you try setting up your cluster domain in Helm charts. Ref: https://github.com/SigNoz/charts/blob/bd2096d909c816519ed4a9ea2f1b6d296da650b1/charts/signoz/values.yaml#L22
a
@Nagesh Bansal hi, sorry for the late response. 1. I tried editing "clusterDomain" in helm chart values.yaml 2. Tried editing the deployment file of the clickhouse operator 3. adding env variables in the helm chart values.yaml I tried above three steps but didn't work. It seems clickhouse-operator config.yaml has hardcoded value of cluster.local Ref: https://github.com/Altinity/clickhouse-operator/blob/4df607eccab30e1a280d9fa6d6bd3dd761001f8c/deploy/builder/templates-config/config.yaml#L79[…]80C1