Version specific upgrade instructions

Overview

Review the instructions provided on this page before you upgrade!

This page provides specific instructions and details of any required manual steps to upgrade to each supported version of SUSE Observability. Any significant change that may impact how SUSE Observability runs after upgrade will be described here, such as a change in memory requirements or configuration.

Read and apply all instructions from the version that you are currently running up to the version that you will upgrade to.

Upgrade instructions

2.10.4

  • The opentelemetry-collector Helm values key has been renamed to otel-receiver, to make clear that it configures a fixed part of the SUSE® Observability platform rather than a general-purpose OpenTelemetry Collector. Rename this block in your values.yaml; leaving the old key in place will cause the deployment to fail, because Helm would otherwise silently ignore everything under it.

    otel-receiver:
  resources:
    limits:
      memory: 512Mi

  • The Kubernetes resources of this component are renamed from suse-observability-otel-collector to suse-observability-otel-receiver, and its app.kubernetes.io/name label changes from opentelemetry-collector to otel-receiver. Update anything that selects on the old names, such as your own NetworkPolicy, ServiceMonitor or PrometheusRule resources, dashboards, and scripts that reference the pod or StatefulSet by name. The OTLP endpoints exposed through the ingress are unchanged.

2.10.0

  • The Helm chart values.yaml has undergone a major refactoring to improve readability and maintainability, you must review the Helm chart migration guide for v2.10.0 and update your values.yaml accordingly.

  • Minio was replaced with S3Proxy, this affects the backup and restore process. If you are using the backup and restore feature (i.e. global.backup.enabled=true), please follow the instructions in the migration guide to migrate your backup and restore configuration to S3Proxy.

2.8.0

  • The installation process has been streamlined by deprecating the mandatory "extra values" generation step. Users are encouraged to follow the Migration Guide to update their existing configurations to the new global mode.

2.7.0

  • The backup.enabled Helm value has been replaced by global.backup.enabled. Using the old backup.enabled=true value will now cause the deployment to fail.

See also