AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    To deploy the Cluster Agent using the AppDynamics Operator, you need a:

    • Cluster Agent Docker Image
    • Secret that contains the Controller access key

    You should create the secret when you deploy the AppDynamics Operator to Kubernetes because it provides the starting configuration for the Cluster Agent.

    Create a Controller Access Key Secret

    To create a secret with a Controller access key:

    $ kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key>

    Create Secret to Pull the Cluster Agent from your Docker Repository

    (Optional) If you are using a Docker repository that requires access credentials, create a secret to pull the Docker image from the private repository:

    $ kubectl -n appdynamics create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=<docker-username> --docker-password=<docker-password> --docker-email=unused

    Then, link the secret to the desired service account:

    kubectl patch serviceaccount -n appdynamics appdynamics-cluster-agent -p '{"imagePullSecrets": [
    {"name": "regcred"}

    ]}'

    Specify this secret in your cluster-agent.yaml file using imagePullSecrets and name property:

    apiVersion: appdynamics.com/v1alpha1
    kind: Clusteragent
    metadata:
      name: k8s-cluster-agent
      namespace: appdynamics
    spec:
      appName: "<app-name>"
      controllerUrl: "http://<appdynamics-controller-host>:8080"
      account: "<account-name>"
      # docker image info

    image: "<docker-registry>/appdynamics/cluster-agent:tag"
    serviceAccountName: appdynamics-cluster-agent
    ### Uncomment the following lines if you need to pull the secrets
    #imagePullSecrets:
    #name: "<docker-pull-secret-name>"


    Deploy the Cluster Agent 

    Start the Cluster Agent and point it to the desired Controller. Deploy the Cluster Agent using the AppDynamics Operator:

    $ kubectl create -f cluster-agent.yaml

    Example output:

    clusteragent.appdynamics.com/k8s-cluster-agent created

    Stop the Cluster Agent

    Stop the Cluster Agent pod: 

    $ kubectl delete -f cluster-agent.yaml

    • No labels