There are three main related strategies for deploying OneAgent on OpenShift, that build upon one another, and offer advantages that are contextual to an organization's standards and preferences.
All three strategies deploy the OneAgent DaemonSet on OpenShift nodes. The DaemonSet is responsible for injecting OneAgent Operator in OpenShift.
The lifecycle of the DaemonSet is typically managed by OneAgent Operator, though you can also choose to deploy the DaemonSet directly using Puppet, Chef, Ansible, or another configuration management tool. Since the Operator can automatically update the Daemonset, we recommend using the Operator rather than the DaemonSet alone.
If you prefer to use Helm as a package manager, you can install OneAgent Operator as a Helm chart. Helm generates both the Operator deployment and the CRD for OneAgent dynamically. This suits perfectly for basic installations of the OneAgent Operator.
Apart from the three main strategies, you can also install the OneAgent Operator via OperatorHub, for a better integration with the OpenShift dashboards.
Finally, if you don't have access to the infrastructure layer, Dynatrace also provides the option of application-only monitoring.