Kubernetes/Openshift Operator for managing Dynatrace OneAgent deployments
The Operator can be upgraded from 0.7.0 with,
# Kubernetes
$ kubectl apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.7.1/kubernetes.yaml
# Openshift
$ oc apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.7.1/openshift.yaml
status.phase
field of the OneAgent object (#197)http_proxy
, etc.) can be ignored on Operator container when skipCertCheck
is true (#204)Operation cannot be fulfilled on oneagents.dynatrace.com \"oneagent\": the object has been modified; please apply your changes to the latest version and try again
openshift.yaml
manifest, see note on README.beta.kubernetes.io/arch
and beta.kubernetes.io/os
labels (#199)v1
instead of v1beta1
for rbac.authorization.k8s.io
objects (#215)The Operator can be upgraded from 0.6.0 with,
# Kubernetes
$ kubectl apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.7.0/kubernetes.yaml
# Openshift
$ oc apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.7.0/openshift.yaml
Additional fields have been added to the OneAgent CRD:
A schema has also been added to the OneAgent CRD:
"2019-10-30T12:59:43.717+0100"
) (#159)tokens
- it needs to be a YAML string now.kubernetes.yaml
and openshift.yaml
, as release attachments rather than having them on the repository code base. For this specific release however, we'll keep both.The Operator can be upgraded from 0.5.x with,
# Kubernetes
$ kubectl apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.6.0/kubernetes.yaml
# Openshift
$ oc apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/download/v0.6.0/openshift.yaml
Service update to get the latest version of the base image for RedHat Container Catalogue where some vulnerabilities have been fixed.
The Dynatrace OneAgent Operator now allows to customize the service account used for creating the OneAgent pods in preparation to release on GKE marketplace.
The Dynatrace OneAgent Operator v0.5.2 fixes a bug introduced in v0.5.1 where the Operator chooses the wrong Secret object for credentials.
The Dynatrace OneAgent Operator v0.5.1 includes a fix for Operator pod crashes when deploying the Operator on a cluster with unschedulable nodes not monitored by the OneAgent.
The Dynatrace OneAgent Operator v0.5.0 includes:
To upgrade from v0.4.0 you can run:
# Kubernetes
$ kubectl apply -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/v0.5.0/deploy/kubernetes.yaml
# OpenShift
$ oc apply -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/v0.5.0/deploy/openshift.yaml
This release version includes a bugfix -
Handles nil pointer panic in oneagent controller when reconciling istio objects - caused by no virtualservice created for IP-based communication hosts.
This release version includes bugfixes -
The enableIstio
feature requires to restart the operator if Istio was deployed after deployment of the operator.
Background: This happens because the cache maintained by controller-runtime's Kubernetes Client is not dynamic. The bug for same is reported here https://github.com/kubernetes-sigs/controller-runtime/issues/321 and the fix for same is currently a work in progress https://github.com/kubernetes-sigs/controller-runtime/pull/554 .