This guide will show you how you can manually migrate from apiVersion: dynatrace.com/v1beta2 to apiVersion: dynatrace.com/v1beta5 of the DynaKube.
Introduced in: Dynatrace Operator version 1.2.0
Deprecated in: Dynatrace Operator version 1.6.0
Last supported in: Dynatrace Operator version 1.6.2
Introduced in: Dynatrace Operator version 1.6.0
When migrating your DynaKube, remember to update the apiVersion field as well as any other fields that have changed
The feature flag that controlled how many mount attempts the CSI driver would make before stopping (feature.dynatrace.com/max-csi-mount-attempts: 5) has been replaced with a timeout-based feature flag. This was done due to the difficulty of determining how many attempts equal a given timeout.
feature.dynatrace.com/max-csi-mount-timeout: "8m" # replaces feature.dynatrace.com/max-csi-mount-attempts: "10"
autoUpdateThe 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/v1beta5kind: DynaKubemetadata:name: examplenamespace: dynatracespec:oneAgent:cloudNativeFullstack: {} # same as autoUpdate: true# ...
If you want autoUpdate: false, set image, codeModulesImage or version
apiVersion: dynatrace.com/v1beta5kind: DynaKubemetadata:name: examplenamespace: dynatracespec:oneAgent:cloudNativeFullstack:image: ... # same effect as autoUpdate: falsecodeModulesImage: # same effect as autoUpdate: false# ...---apiVersion: dynatrace.com/v1beta5kind: DynaKubemetadata:name: examplenamespace: dynatracespec:oneAgent:cloudNativeFullstack:version: ... # replaces autoUpdate: false# ...
spec.applicationMonitoring.useCSIDriverThe spec.applicationMonitoring.useCSIDriver: true/false field has been removed.
The CSI driver is now used when installed as part of the Dynatrace Operator installation.