Try it free

Migration of DynaKube v1beta3 to v1beta4

  • Latest Dynatrace
  • Reference
  • 10-min read

This guide will show you how you can manually migrate from apiVersion: dynatrace.com/v1beta3 to apiVersion: dynatrace.com/v1beta4 of the DynaKube.

DynaKube API version v1beta4 was removed from the CRD in Dynatrace Operator version 1.11.0. On Operator version 1.11.0 or later you can no longer apply v1beta4 resources. Use this guide only if you're on Operator version 1.10.0 or earlier; otherwise migrate directly to v1beta6 or v1beta5.

Support lifecycle

v1beta3

Introduced in: Dynatrace Operator version 1.4.0

Deprecated in: Dynatrace Operator version 1.6.0

v1beta4

Introduced in: Dynatrace Operator version 1.5.0

Deprecated in: Dynatrace Operator version 1.9.0

Last supported in: Dynatrace Operator version 1.10.0

Changes

Reminder

When migrating your DynaKube, remember to update the apiVersion field as well as any other fields that have changed

Deprecated fields

OneAgent autoUpdate

The spec.oneAgent.<mode>.autoUpdate: true/false field is deprecated in v1beta5, so it shouldn't be used.

We recommend the following:

  • If you want autoUpdate: true, do not set image, codeModulesImage, or version.

    apiVersion: dynatrace.com/v1beta5
    kind: DynaKube
    metadata:
    name: example
    namespace: dynatrace
    spec:
    oneAgent:
    cloudNativeFullstack: {} # same as autoUpdate: true
    # ...
  • If you want autoUpdate: false, set image, codeModulesImage or version

    apiVersion: dynatrace.com/v1beta5
    kind: DynaKube
    metadata:
    name: example
    namespace: dynatrace
    spec:
    oneAgent:
    cloudNativeFullstack:
    image: ... # same effect as autoUpdate: false
    codeModulesImage: # same effect as autoUpdate: false
    # ...
    ---
    apiVersion: dynatrace.com/v1beta5
    kind: DynaKube
    metadata:
    name: example
    namespace: dynatrace
    spec:
    oneAgent:
    cloudNativeFullstack:
    version: ... # replaces autoUpdate: false
    # ...
Related tags
Dynatrace Platform