Migrate from OneAgent Operator to Dynatrace Operator
Understand and configure the DynaKube custom resource
The DynaKube custom resource (CR) replaces the OneAgent custom resource. The DynaKube CR follows the "don't repeat yourself" (DRY) principle to deploy a number of different components to your Kubernetes cluster.
Each section includes an illustration of the differences between the two custom resources, what changes from the old custom resource to the new one (marked with green), and what stays the same in both custom resource (marked with blue).
Changing operators will change the host ID calculations for monitored hosts, which will lead to monitoring anomalies in the Dynatrace UI.
Classic full-stack migration
Follow the instructions below to migrate from OneAgent Operator to Dynatrace Operator for classic full-stack injection.
Global parameters (spec)
The following settings are global, shared by every component, and located under spec.
This was disableAgentUpdate in the OneAgent CR. The values are flipped for this field: disableAgentUpdate: true means autoUpdate: false. The default is still to enable automatic updates.
2
This was agentVersion in the OneAgent CR.
All the other OneAgent parameters (such as tolerations, arguments, DNS, and resource settings) are also located in the .spec.oneAgent.classicFullStack section and are unique to the full-stack installation.
Application-only migration
Follow the instructions below to migrate from OneAgent Operator to Dynatrace Operator for automatic application-only injection.
Global parameters (spec)
The following settings are global, shared by every component, and located under spec.
ApplicationMonitoring parameters (.spec.oneAgent.applicationMonitoring)
A new section for the full-stack OneAgent is located at .spec.oneAgent.applicationMonitoring:
This new parameter will deliver binaries to pods automatically and eliminate storage requirements on pods. This is in preview only and defaults to false.
The image parameter is no longer available. The functionality will be reintroduced in future. For now, all pods download from the API URL.
Migrate from OneAgent Operator to Dynatrace Operator
You can migrate from the deprecated OneAgent Operator to the new Dynatrace Operator that manages the lifecycle of several Dynatrace components such as OneAgent, routing, and Kubernetes API Monitor. Additional components will be added as new observability features become available.
Select one of the following options, depending on your deployment methods.
