Download page Install the Cluster Agent with OpenShift OperatorHub Bundle.
Install the Cluster Agent with OpenShift OperatorHub Bundle
This page describes how to install the Cluster Agent using the Splunk AppDynamics OpenShift OperatorHub Bundle which is an alternative to Install the Cluster Agent with Kubernetes CLI.
Splunk AppDynamics OpenShift OperatorHub Bundle is available at RedHat catalog.
Edit cluster-agent.yaml to set the Splunk AppDynamics Controller details for the Cluster Agent to report to. a. Set the nsToMonitorRegex options to include the namespaces you want to monitor. b. Set the image tag to the version you are installing. Refer to Cluster Agent Red Hat image for the latest version tag. For additional configuration tasks, see Configure the Cluster Agent.
This example assumes the use of the pre-built Cluster Agent image on RedHat Registry. See Cluster Agent Container Image to build your own image.
apiVersion: cluster.appdynamics.com/v1alpha1
kind: Clusteragent
metadata:
name: k8s-cluster-agent
namespace: appdynamics
spec:
appName: "dev-cluster"
controllerUrl: "http://mycontroller.com:8080"
account: "my-account"
# docker image info where, <version> is the image tag version that you are installing
image: "docker.io/appdynamics/cluster-agent:<version>"
serviceAccountName: appdynamics-cluster-agent
nsToMonitorRegex: namespace1|namespace2
stdoutLogging: "true"
YML
Install the Cluster Agent:
kubectl create -f cluster-agent.yaml
CODE
Check appdynamics-operator and appdynamics-cluster-agent pods are running. Also, Check Catalogsource, Subscription and Clusterserviceversion are created:
# Cisco Appdynamics Operator pod status
kubectl get pods -n appdynamics
# CA pod status
kubectl get pods -n appdynamics
# catalogsources should be created
kubectl get catalogsources -n appdynamics
# subscriptions should be created
kubectl get subscriptions -n appdynamics
# ClusterServiceVersion should be created
kubectl get clusterserviceversion -n appdynamics