Skip to content

Latest commit

 

History

History
24 lines (15 loc) · 1.33 KB

v2-18-migration.md

File metadata and controls

24 lines (15 loc) · 1.33 KB
Raw

Upgrading from v2.17 to v2.18

Upgrade OpenTelemetry Operator CRDs

Do I need to do this?

You need to do this if you have the OpenTelemetry Operator subchart enabled with opentelemetry-operator.enabled: true in your values file.

What do I need to do?

Run the following commands on the cluster before upgrading the chart:

kubectl apply --server-side --force-conflicts --filename https://raw.githubusercontent.com/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator-0.24.0/charts/opentelemetry-operator/crds/crd-opentelemetrycollector.yaml
kubectl apply --server-side --force-conflicts --filename https://raw.githubusercontent.com/open-telemetry/opentelemetry-helm-charts/opentelemetry-operator-0.24.0/charts/opentelemetry-operator/crds/crd-opentelemetryinstrumentation.yaml

Why do I need to do this?

The OpenTelemetry Operator subchart was upgraded from v0.13.0 to v0.18.3. The new chart introduces a new feature in the Instrumentation CRD. If you do not upgrade the CRDs, the release-name-ot-operator-instr job will fail.