Skip to main content

Kubernetes

Once you have successfully installed SigNoz on Kubernetes, the following sections provide an overview of the activities that are required to successfully operate SigNoz.

Stop/Start

To stop the running SigNoz cluster:

helm -n platform uninstall "my-release"

To start/resume the running SigNoz cluster:

helm -n platform install "my-release"

Note: The newly created release aka SigNoz cluster should mount to the existing persistent volume as long as the namespace and the release name* matches to the old one.

Upgrade

Use the steps below to upgrade to the latest:

  1. Fetch the latest chart information from the Helm repositories
helm repo update
  1. Upgrade to the latest available version of the chart
helm -n platform upgrade my-release signoz/signoz
info

To override values in a Helm chart, you can also use the values/-f flag. See the Helm Upgrade page of the Helm documentation for more details.

In case you wish to upgrade the SigNoz cluster to a specific version, follow the steps below:

  1. List the available SigNoz Helm charts with their version and supported app version.
helm search repo signoz --versions

The output should look similar to the following:

NAME                CHART VERSION   APP VERSION DESCRIPTION
signoz/signoz 0.0.9 0.7.1 SigNoz Observability Platform Helm Chart
signoz/signoz 0.0.8 0.6.2 SigNoz Observability Platform Helm Chart
signoz/signoz 0.0.7 0.6.1 SigNoz Observability Platform Helm Chart
signoz/signoz 0.0.6 0.6.1 SigNoz Observability Platform Helm Chart
signoz/alertmanager 0.5.2 0.5.0 The Alertmanager handles alerts for SigNoz.
signoz/clickhouse 16.0.2 21.12.3.32 A Helm chart for ClickHouse
  1. Run the following command to install the chart version 0.0.8 running SigNoz version 0.6.2 with the release name my-release and namespace platform:
helm -n platform upgrade my-release signoz/signoz --version 0.0.8
warning
  • Be careful with breaking changes across versions!
  • There might be misconfiguration caused by version mismatch.

Uninstall

To uninstall/delete the my-release resources:

helm -n platform uninstall "my-release"

See the Helm docs for documentation on the helm uninstall command.

The command above removes all the Kubernetes components associated with the chart and deletes the release.

Deletion of the StatefulSet doesn't cascade to deleting associated PVCs. To delete them:

kubectl -n platform delete pvc --selector app.kubernetes.io/instance=my-release

Sometimes everything doesn't get properly removed. If that happens try deleting the namespace:

kubectl delete namespace platform

Remove the Sample Application

Use the command below to remove the sample application:

curl -sL https://github.com/SigNoz/signoz/raw/main/sample-apps/hotrod/hotrod-delete.sh \
| HOTROD_NAMESPACE=sample-application bash

Increase the ClickHouse Persistent Volume Size on EKS/GKE

You can use the following helm upgrade command to increase the size of the persistent volume used by SigNoz on EKS/GKE, replacing the following values to match your environment:

  • Your namespace (this example uses platform)
  • Your release (this example uses my-release)
  • Your chart (this example uses signoz/signoz)
  • The new size of the persistent volume (this example uses 25Gi)
helm -n platform upgrade my-release signoz/signoz \
--set clickhouseOperator.storage=25Gi
info

To override values in a Helm chart, you can also use the values/-f flag. See the Helm Upgrade page of the Helm documentation for more details.