Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.


Skip to end of metadata
Go to start of metadata

To install the AppDynamics Operator, open a command prompt and follow the steps below. If you are not on Kubernetes, see Deploy the AppDynamics Operator on Red Hat OpenShift.

This document contains links to Kubernetes documentation. AppDynamics makes no representation as to the accuracy of Kubernetes documentation because Kubernetes controls its own documentation.

  1. Ensure your kubectl is pointing to your Kubernetes cluster. For more details see, Install and Set Up kubectl in the Kubernetes documentation.

  2. Log on as a cluster administrator.

  3. Create a namespace for appdynamics in your Kubernetes cluster:

    $ kubectl create namespace appdynamics
  4. Verify your namespace is created by running:

    $ kubectl get namespace

    Example output:

    NAME				STATUS			AGE
    appdynamics			Active			5s
    default				Active			41d
    kube-node-lease		Active			41d
    kube-public			Active			41d
    kube-system			Active			41d
  5. To install the latest version of the AppDynamics Operator for Kubernetes, run:

    $ kubectl create -f cluster-agent-operator.yaml

    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
  6. To verify that the AppDynamics Operator is running, enter:

    kubectl -n appdynamics get pods

    Example output:

    NAME									READY		STATUS		RESTARTS	AGE
    appdynamics-operator-95ffb549c-m8tjv	1/1			Running		0			30s

    This output shows that Kubernetes extends the custom resource definitions that you provided. Now you are ready to Build the Cluster Agent Container Image.

  • No labels