This is the home of Dynatrace OneAgent Operator which supports the rollout and lifecycle of Dynatrace OneAgent in Kubernetes and OpenShift clusters. Rolling out Dynatrace OneAgent via DaemonSet on a cluster is straightforward. Maintaining its lifecycle places a burden on the operational team. Dynatrace OneAgent Operator closes this gap by automating the repetitive steps involved in keeping Dynatrace OneAgent at its latest desired version.

Dynatrace OneAgent Operator is based on Operator SDK and uses its framework for interacting with Kubernetes and OpenShift environments. It watches custom resources OneAgent and monitors the desired state constantly. The rollout of Dynatrace OneAgent is managed by a DaemonSet initially. From here on Dynatrace OneAgent Operator controlls the lifecycle and keeps track of new versions and triggers updates if required.

The Dynatrace OneAgent Operator acts on its separate namespace dynatrace. It holds the operator deployment and all dependent objects like permissions, custom resources and corresponding DaemonSets.

$ kubectl create -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/namespace.yaml
$ kubectl create -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/rbac.yaml

$ kubectl create -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/crd.yaml
$ kubectl create -f https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/operator.yaml

The activity of Dynatrace OneAgent Operator can be observed by following its logs:

$ kubectl -n dynatrace logs -f deployment/dynatrace-oneagent-operator

The rollout of Dynatrace OneAgent is governed by a custom resource of type OneAgent:

apiVersion: "dynatrace.com/v1alpha1"
kind: "OneAgent"
metadata:
  # a descriptive name for this object.
  # all created child objects will be based on it.
  name: "example"
  namespace: "dynatrace"
spec:
  # dynatrace api url including `/api` path at the end
  apiUrl: "https://ENVIRONMENTID.live.dynatrace.com/api"
  # dynatrace api token: `/#settings/integration/apikeys`
  apiToken: ""
  # dynatrace paas token (aka installer token): `/#settings/integration/paastokens`
  paasToken: ""
  # node selector to control the selection of nodes (optional)
  nodeSelector: {}
  # https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ (optional)
  tolerations: []

Save the snippet to a file or use ./deploy/cr.yaml from this repository and adjust its values accordingly. Create the custom resource:

$ kubectl create -f cr.yaml

The status of the Dynatrace OneAgent rollout can be observed by watching the pod list:

$ kubectl -n dynatrace get pods --selector=dynatrace=oneagent,oneagent -w -o wide

See HACKING for details on how to get started enhancing Dynatrace OneAgent Operator.

See CONTRIBUTING for details on submitting changes.

Dynatrace OneAgent Operator is under Apache 2.0 license. See LICENSE for details.