Dynatrace Operator release notes version 1.0.0
Release date: Mar 25, 2024
Announcements
We now recommend using Helm as the preferred installation method.
- A warning has been been added when using
ONEAGENT_INSTALLER_SCRIPT_URLand/orONEAGENT_INSTALLER_TOKENenvironment variables within the DynaKube, as they are unsupported.
- Custom proxy settings via DynaKube are ignored by the OneAgent due to
NO_PROXYbeing set by default. This change only impacts communication via ActiveGates.
New features and enhancements
-
OneAgent version 1.273+ Dynatrace Operator now passes on proxy configuration from DynaKube via files for security reasons. The respective files can be found at the following paths:
-
OneAgent pods:
/var/lib/dynatrace/secrets/internal-proxy -
Code modules:
/opt/dynatrace/oneagent-paas/agent/conf/ruxitagentproc.conf
-
- As a new default, Dynatrace Operator deployments (
operator,webhook, andcsi-driver) use images from the Dynatrace repository on Amazon ECR to minimize throttling risks during the scaling of larger clusters.
- Dynatrace version 1.283+ Host group information is now utilized when requesting code module configurations from the environment. For older cluster versions, the host group will be disregarded.
- A new annotation has been introduced to allow the exclusion of specific containers from injection. To apply this, add
container.inject.dynatrace.com/<container-name>: "false"to your DynaKube configuration or directly to a specific pod.
The configuration of each component is now managed independently, for example, ensuring that issues in ActiveGate configuration do not affect OneAgent configuration.
- EdgeConnect instances managed by Dynatrace Operator (with the
managedByattribute set) now support the following automated error recovery scenarios:An EdgeConnect instance with the same name as the custom resource already exists in the environment.
An EdgeConnect instance needs to be recreated in the environment because the client secret is missing.
- An EdgeConnect instance must be recreated in the environment due to an invalid
EdgeConnectId.
-
In release manifests, images are now pinned to the corresponding digest using the format
<version>@sha.For example
image: public.ecr.aws/dynatrace/dynatrace-operator:v1.0.0@sha256:f89...e811
- The names of components related to Dynatrace Operator deployment has been updated to
dynatrace-operator, instead of using the custom name set by the Helm chart. This change does not apply if the recommended installation instructions for Helm or manifests were followed.
- Enhanced the support archive to include the following resources:
MutatingWebhookConfigurationValidatingWebhookConfigurationCustomResourceDefinitionconfigMapsfrom Dynatrace Operator namespace.
- The
csiReadOnlyanduseCSIDriverfields have been moved from environment variables to the injection secret for injected pods, enhancing consistency.
- All feature flags marked as deprecated that begin with
alpha.operator.dynatrace.com/feature-have been removed.
- The
.spec.oneAgent.hostGroupfield has been added to DynaKube to allow host group configuration across all deployment modes. The existing configuration via command arguments remains functional, however the dedicated field is prioritized when both options are specified.
Resolved issues
- A validation has been added for the
matchExpressionscomponent of the namespace selector in the DynaKube configuration.
- The
ruxitagentproc.conffile is no longer overwritten for code modules that have already been injected over time.
- Fixed an issue where the Dynatrace Operator version was incorrectly reported as
snapshotin the component log lines of Dynatrace Operator version 0.15.0.
- In case the
--set-host-id-sourceargument is specified in the DynaKube, it does not appear twice in the final OneAgent argument list. The argument specified in the DynaKube will take precedence over any default settings. This update will also cause OneAgent pods to restart upon upgrading the Dynatrace Operator.
- Fixed an issue where code modules were incorrectly pulled through
codeModulesImagefor architectures other than amd64.
Upgrade from Dynatrace Operator version 0.15.0+
Changes in this version:
Dynatrace Operator OCI-based Helm chart from Amazon ECR is the recommended installation method for Dynatrace Operator.
- Helm The CSI driver deployment has been updated to occur by default. To avoid deploying the CSI driver, it must be explicitly disabled:
- Ensure
csidriver.enabledis set to false in the Helm chart values.
- Ensure
- Manifests No change in behaviour, only apply kubernetes.yaml or openshift.yaml if CSI driver is not needed.