Migration guides for DynaKube apiVersions

Overview

Depending ony our Dynatrace Operator Version, different apiVersion's of the DynaKube are supported. This page collects the migration guides for each apiVersion considering the version of the Operator.

API Version Overview

DynaKube API versionIntroducedDeprecatedRemovedMigration guides
v1beta51.6.0
v1beta41.5.0
v1beta31.3.01.6.0
v1beta21.2.01.6.01.7.0to v1beta5
v1beta10.3.01.6.01.7.0to v1beta5

Conversion strategies

Automatic conversion

Each version of the Dynatrace Operator converts the deployed DynaKubes with an older apiVersion to the latest apiVersion supported by that Dynatrace Operator version.

  • Example: Dynatrace Operator v1.6.x will always convert DynaKubes to v1beta5.

So when you are checking, using kubectl what apiVersion you are using, you will always see the latest apiVersion that is supported by that Dynatrace Operator version. You can facilitate this mechanism instead of doing a manual conversion.

  1. Download the converted version of your DynaKube. The following command will give you the DynaKube converted to the latest supported apiVersion:

    kubectl get dynakubes -n <namespace> <dynakube-name> -o yaml
  2. Cleanup the downloaded DynaKube, only keep this sections

    • relevant parts of .metadata section
    • complete .spec section

Manual conversion

  1. First, check the version of the Operator that is currently deployed. If you don't know which version you're running, here are some ways to find out.

    Using Helm:

    • Use the helm list command, the APP VERSION field tells you the version of the installed Dynatrace Operator.
      • Example:
    > helm list -n dynatrace -o json | jq -r '.[].app_version'`
    1.6.2

    Using kubectl:

    • There is an app.kubernetes.io/version label on the Dynatrace Operator Deployment that shows the version used.
      • Example:
    > kubectl get deployment dynatrace-operator -n dynatrace -o jsonpath='{.metadata.labels.app\.kubernetes\.io/version}'
    1.6.2
  2. Then check the apiVersion of the DynaKube used and follow the matching migration guide in the overview above.