This message was deleted.
# general
s
This message was deleted.
p
hi @User Welcome to SigNoz community šŸ‘‹
Do you mean the clickhouse-operator in k8s folder ?https://github.com/SigNoz/signoz/tree/main/deploy/kubernetes/platform/crds
d
yes
Hello @User, If I want to deploy SigNoz on Digitalocean kubernetes cluster, what procedure do I need to follow?
p
we have tested the current helm charts for AWS and Azure
but I think, you change this line to something other than aws or gcp - it should work
you can try - would be curious to know if that works
cloud : digitalocean
cc @User if you have any more inputs
a
that should work
what is the purpose of clickhouse-operator in SigNoz?
@User clickhouse does not have a maintained helm chart but a k8s-operator. We extracted the CRD and needed files in templates for our use at SigNoz
d
cloud : digitalocean I will try this
I tried. It's working.
šŸ™Œ 1
I have another doubt. can I use my existing alertmanager in SigNoz?
a
Never tried though but it should work. We forked the alertmanager to provide rest APIs to add channels from signoz frontend. Like in this img. But you can set up your own alertmanager with yamls to make it work
d
okay I'll try let you know. but for now I am deploying in digitalocean kubernetes cluster right, I can give minimum volume size 1Gi , for alertmanager I tried to update volume size in values.yaml file
this is the error I got
a
Yes dynamically changing size of PVC in stateful set is not permitted
this should be enabled using
allowVolumeExpansion : true
in storage class
Do you have know how of helm charts? We enabled this for clickhouse. We can follow same steps for alertmanager also and you can submit a PR for this too
d
okay
aws and gcp clouds you are creating separate storageclass for clickhouse-operator right?
a
yes
same to be done for alertmanager and for all clouds
for volume size to change dynamically
d
can I disable alertmanager installation? I tried it but didn't work
@User
a
alertmanager cannot be disabled now using
values.yaml
file. Please raise a github issue for this. Though this seems doable by • commenting https://github.com/SigNoz/signoz/blob/main/deploy/kubernetes/platform/Chart.yaml#L35-L37 • commenting https://github.com/SigNoz/signoz/blob/main/deploy/kubernetes/platform/signoz-charts/query-service/templates/prometheus-configmap.yaml#L14-L18 • running
helm dependency update deploy/kubernetes/platform