v1.0.0-rc.0

⚠️ This is a pre-release, which has no official support by Dynatrace. If you run into issues with this specific release, please open a Github Issue!

Release notes for v1.0.0 will be published in our official documentation.

Installation

For information on how to install the latest dynatrace-operator please visit our official Documentation.

Helm (recommended)

helm upgrade dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator   --version 1.0.0-rc.0   --create-namespace --namespace dynatrace   --install   --atomic

Other upgrade/install instructions

Kubernetes

kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v1.0.0-rc.0/kubernetes.yaml

Openshift

oc apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v1.0.0-rc.0/openshift.yaml

Features

• Changed the operators behaviour when interacting with private image registries, which means the operator does not need to have a customPullSecret anymore incase a private registry is used and the nodes are already authenticated (ECR, GCR, ACR,..). No image manifest gets pulled anymore. Auto-update now has to happen manually by updating the image field of the Dynakube. Incase custom images are used the operator requires OneAgent version 1.276+)
• Introduced an annotation to allow exclusion of specific containers from injection. To do so, add container.inject.dynatrace.com/: "false" to your Dynakube or a specific pod.
• Host group is now used when requesting code module configuration from the Tenant (requires cluster version 283+). For older Cluster versions, the Host group will be ignored.
• Set NO_Proxy for ActiveGate communication endpoints within OneAgent configuration, in order to allow direct traffic when custom proxy is used.
• Update names for Operator deployment related components to dynatrace-operator instead of using the custom name of the Helm chart (if set). There is no change if recommended Installation instructions for helm or manifests were used.
• Starting from OneAgent version 1.273.0, Dynakube's proxy value is mounted in a file instead of passing it as an argument or environment variable
• Ensure that each component's configuration is treated independently e.g issues in ActiveGate configuration do not interfere with OneAgent configuration
• EdgeConnects that are managed by the Operator (managedBy Attribute set) now support following automated error recovery scenarios:
  EdgeConnect on the tenant already exists (has the same name as the CR)
  EdgeConnect on the tenant has to be recreated because the client secret is missing3) EdgeConnect on the tenant has to be
  recreated due to invalid EdgeConnectId
• Moved the fields csiReadOnly and useCSIDriver from env vars into the injection Secret for injected Pods in order to be more consistent
• Added a warning when using ONEAGENT_INSTALLER_SCRIPT_URL and/or ONEAGENT_INSTALLER_TOKEN env vars within the Dynakube, as they are not supported
• Enhanced the support archive with following resources:
  MutatingWebhookConfiguration
  ValidatingWebhookConfiguration
  CustomResourceDefinition
  configMaps from the operator's namespace

Fixes

• Fixed a problem, where the operator version was unexpectedly reported as "snapshot" in operator version 0.15.0 within the operators component log lines.
• It is now made sure that If the --set-host-id-source argument is specified in the Dynakube it doesn't show up twice in the final OneAgent argument list. The argument specified in the Dynakube takes precedence over any defaults that would be applied.Note also that this causes a restart ofOneAgent pods upon upgrading Dynatrace Operator.
• The ruxitagenproc.conf is no longer overwritten for already injected codemodules overtime

Full changelog will be published with the final release, including bugfixes and further smaller improvements!