Upgrade and Uninstall

Robusta is installed with Helm, so Robusta upgrades are just Helm upgrades. Uninstalls are just Helm uninstalls.


Upgrading an existing release with bundled Prometheus Stack might require manual actions. Read here

Helm Upgrade

This will upgrade Robusta while preserving any custom settings:

helm repo update
helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=<YOUR_CLUSTER_NAME>

We recommend running the above command by changing nothing more than the "clusterName".

Where is my generated_values.yaml?

If you have lost your generated_values.yaml file, you can extract it from the cluster:

helm get values -o yaml robusta > generated_values.yaml

Verify that Robusta is running and there are no errors in the logs:

robusta logs


1. We do not recommend running helm upgrade --reuse-values as it doesn't update default values changed in the chart.

  1. To install a Robusta pre-release, run helm upgrade with the --devel flag.

Upgrading with bundled Prometheus Stack

If you didn't install Robusta's bundled Prometheus Stack then you can upgrade at ease. Otherwise, keep reading.

Why do I need to manually upgrade?

Robusta uses kube-prometheus-stack, which creates custom resources also known as CRDs on installation. With Helm v3, CRDs are not updated or removed by default and should be manually handled. Consult also the Helm Documentation on CRDs.

Upgrading from older versions (0.10.8 and below)

  1. Determine Robusta's version by running the following:

helm list
  1. The node-exporter daemonset and admission webhooks needs to be manually removed prior to upgrading:

kubectl delete daemonset -l app=prometheus-node-exporter
kubectl delete validatingwebhookconfigurations.admissionregistration.k8s.io -l app=kube-prometheus-stack-admission
kubectl delete MutatingWebhookConfiguration -l app=kube-prometheus-stack-admission
  1. Manually update the installed CRDs (for more info read here):


If you have an existing Prometheus Operator installed independently of Robusta then be very careful! Upgrading CRDs will impact all Prometheus Operators in your cluster.

kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagerconfigs.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagers.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_podmonitors.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_probes.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_prometheuses.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_prometheusrules.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml
kubectl replace -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.61.1/example/prometheus-operator-crd/monitoring.coreos.com_thanosrulers.yaml
  1. Update helm chart and upgrade Robusta (where is my generated_values.yaml):

helm repo update && helm upgrade robusta robusta/robusta -f ./generated_values.yaml
  1. Verify that Robusta is running and there are no errors in the logs:

robusta logs

Helm Uninstall

This will uninstall Robusta:

helm uninstall robusta