This document contains links to Red Hat OpenShift documentation. AppDynamics makes no representation as to the accuracy of Red Hat OpenShift documentation because Red Hat controls its own documentation.
Ensure your oc is pointing to your Kubernetes cluster. For more details see, Get Started with the CLI in the Red Hat OpenShift documentation.
Log on as a cluster administrator.
Create a namespace for appdynamics in your Red Hat OpenShift cluster:
$ oc new-project appdynamics
CODE
Verify your namespace is created by running:
$ oc get project
CODE
Example output:
NAME DISPLAY NAME STATUS
appdynamics Active
default Active
kube-public Active
kube-service-catalog Active
kube-system Active
TEXT
To install the latest version of the AppDynamics Operator for Red Hat OpenShift
The AppDynamics Operator creates a Custom Resource Definition, which extends the Kubernetes APIs to create a new Kubernetes type called clusteragents. The AppDynamics Operator also creates a serviceaccount, a clusterrole, and clusterrolebinding for the namespace.
Example output:
customresourcedefinition.apiextensions.k8s.io/clusteragents.appdynamics.com created
customresourcedefinition.apiextensions.k8s.io/infravizs.appdynamics.com created
serviceaccount/appdynamics-operator created
serviceaccount/appdynamics-infraviz created
podsecuritypolicy.extensions/appdynamics-infraviz created
clusterrole.rbac.authorization.k8s.io/appdynamics-operator created
clusterrolebinding.rbac.authorization.k8s.io/appdynamics-operator created
clusterrolebinding.rbac.authorization.k8s.io/appdynamics-infraviz created
role.rbac.authorization.k8s.io/appdynamics-infraviz created
rolebinding.rbac.authorization.k8s.io/appdynamics-infraviz created
deployment.apps/appdynamics-operator created
CODE
Verify that the AppDynamics Operator is running:
oc -n appdynamics get pods
CODE
Example output:
NAME READY STATUS RESTARTS AGE
appdynamics-operator-95ffb549c-m8tjv 1/1 Running 0 30s