To enable auto-instrumentation, you:

• Add additional configuration to the cluster-agent.yaml file, or
• Add configuration to the Cluster Agent Helm Chart values.yaml file. See Install the Cluster Agent with Helm Charts.

Then, you can apply the changes using kubectl or upgrade the Cluster Agent Helm Chart.

When the Cluster Agent detects a supported workload, and the workload matches the configured auto-instrumentation rules, the Cluster Agent modifies the workload's spec using the Kubernetes API. The Cluster Agent attaches an init container with the Splunk AppDynamics .NET Core, Node.js, or Java Agent image to the workload. If a volume has the prefix as appd, the Cluster Agent deletes the volume from the workload to ensure that during the next auto-instrumentation there is no error. When the application restarts, the required agent is copied into the application container. As a result, the application container references the Splunk AppDynamics agents (Node.js Agent, .NET Core on Linux Agent, or Java Agent) in an auto-instrumented application.