Issue with Custom Node Selector in ClickhouseInstacne
TLDR Sony is having trouble with the custom Node selector in ClickhouseInstance. It seems the config isn't transferred to the chi pods they create. They've also raised this issue on GitHub.
Sony
Wed, 08 Nov 2023 07:18:25 UTC```clickhouse: installCustomStorageClass: true nodeSelector: component: stateful tolerations: - effect: NoSchedule key: component operator: Equal value: stateful persistence: size: 15Gi resources: requests: cpu: 1000m memory: 1000Mi limits: cpu: 2000m memory: 4Gi settings: prometheus/endpoint: /metrics prometheus/port: 9363 prometheus/metrics: true prometheus/events: true prometheus/asynchronous_metrics: true zookeeper: nodeSelector: component: stateful tolerations: - effect: NoSchedule key: component operator: Equal value: stateful clickhouseOperator: nodeSelector: component: stateful tolerations: - effect: NoSchedule key: component operator: Equal value: stateful```
Sony
Wed, 08 Nov 2023 07:18:42 UTCAlso raised an issue on github
SigNoz Community
Indexed 1061 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Sony
Wed, 08 Nov 2023 07:18:07 UTCHello, We are not able to use custom Node selector when it comes to ClickhouseInstacne. The config is not being passed to the chi pods that are being created. With clickhouse operator its working fine though. Please let me know if I am missing something Attching my config :point_down: