Try it free

Migration of DynaKube v1beta4 to v1beta6

  • Latest Dynatrace
  • Reference
  • 5-min read

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

Support lifecycle

v1beta4

Introduced in: Dynatrace Operator version 1.5.0

Deprecated in: Dynatrace Operator version 1.9.0

v1beta6

Introduced in: Dynatrace Operator version 1.8.0

Changes

Reminder

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

Renamed fields

spec.activeGate.persistentVolumeClaim

The spec.activeGate.persistentVolumeClaim field has been renamed to spec.activeGate.volumeClaimTemplate. The functionality remains the same.

Deprecated fields

OneAgent autoUpdate, version

The spec.oneAgent.<mode>.autoUpdate: true/false field is deprecated in v1beta5 and the spec.oneAgent.<mode>.version field is deprecated in v1beta6, 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/v1beta6
    kind: DynaKube
    metadata:
      name: example
      namespace: dynatrace
    spec:
      oneAgent:
        cloudNativeFullstack: {} # same as autoUpdate: true
        # ...

  • If you want autoUpdate: false, set image, codeModulesImage

    apiVersion: dynatrace.com/v1beta6
    kind: DynaKube
    metadata:
      name: example
      namespace: dynatrace
    spec:
      oneAgent:
        cloudNativeFullstack:
          image: ... # same effect as autoUpdate: false
          codeModulesImage: # same effect as autoUpdate: false
        # ...

Moved fields

spec.extensions

The spec.extensions field was moved to spec.extensions.prometheus to accommodate the new spec.extensions.databases field. The functionality remains the same.

Related tags
Dynatrace Platform