Installation
For information on how to install the dynatrace-operater please visit our official Documentation.
Warning The Operator can be upgraded from the last release with, the following commands.
The Operator's helm chart can be upgraded from the last version with,
Upgrade instructions
When upgrading from v0.9.0
additional steps are required when CSI driver was in use. For more information check out the blog post on upgrade issues from v0.9.0
to a different version.
Kubernetes (with CSI driver)
kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/kubernetes.yaml
kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/kubernetes-csi.yaml
Kubernetes (default)
kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/kubernetes.yaml
Openshift (with CSI driver)
oc apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/openshift.yaml
oc apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/openshift-csi.yaml
Openshift (default)
oc apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.10.0/openshift.yaml
Helm
helm repo update
helm upgrade dynatrace-operator dynatrace/dynatrace-operator --reuse-values --atomic --version="0.10.0"
What's Changed
Warning
Activegate Authtoken support is now enabled by default
- requires additional api token scope:
activeGateTokenManagement.create
feature.dynatrace.com/activegate-authtoken=false
to disable
- Propagation of build labels from pod to environment variables (official documentation)
- Allow configuration of CSI driver log garbage collection interval (official documentation)
- Add pod annotation to disable webhook injection completely
dynatrace.com/inject=false
to disable webhook injection for a pod in a monitored namespace
- Troubleshoot command improvements
- All Dynakubes in the given namespace will be analyzed, unless --dynakube parameter is provided
- Show all errors that can be detected by the troubleshoot command, instead of stopping after the first error
- Add recommended LABELS to the Dockerfile and released image
docker inspect docker.io/dynatrace/dynatrace-operator:v0.10.0
- Add configurable labels/annotations for oneagent and activegate to the Dynakube
Feature Flags
- ➕ Add feature flag to configure release label propagation
feature.dynatrace.com/label-version-detection=true
- ➕ Add environment variable to configure more aggressive garbage collection on the CSI driver
MAX_UNMOUNTED_VOLUME_AGE
environment variable on theprovisioner
container of the CSI driver pod sets the interval in days
Helm changes ⛑️
- Add
csidriver.maxUnmountedVolumeAge
to setMAX_UNMOUNTED_VOLUME_AGE
environment variable
Bugfixes 🪲
- Fix missing pod metadata for the enrichment file in case oneagent injection is disabled
- Fix Activegate statefulset recreation when labelled externally
- Fix custom image handling in troubleshoot command
- Fix missing
readOnlyRootFilesystem
for Activegate init container in case feature flag is set - Reduce default memory usage for operator components by reducing logger instances
- Lower default CSI driver oneagent log garbage collection interval to 7 days
Full Changelog: v0.9.1...v0.10.0