Controller accessKey

Required

Password for local user from the Controller.

Required only when auto-instrumentation is enabled.

Username for local user from the Controller.

Required only when auto-instrumentation is enabled.

How often Kubernetes warning and state-change events are uploaded to the Controller in seconds. See Monitor Kubernetes Events.

If no response is received from the Controller, number of seconds after which the server call is terminated.

Credential file used to authenticate when pulling images from your private Docker registry or repository. Based on your Docker registry configuration, you may need to create a secret file for the Splunk AppDynamics Operator to use when pulling the image for the Cluster Agent. See Create a Secret by providing credentials on the command line.

The maximum number of times Cluster Agent checks for the successful rollout of instrumentation before marking it as failed.

Maximum file size of the log in MB.

Maximum number of backups saved in the log. When the maximum number of backups is reached, the oldest log file after the initial log file is deleted.

Number of log details. INFO, WARNING, DEBUG, or TRACE.

Number of lines to be tailed while collecting logs.

To use this parameter, enable the log capturing feature. See Enable Log Collection for Failing Pods.

By default, the Cluster Agent writes to a log file in the logs directory. Additionally, the stdoutLogging parameter is provided to send logs to the container stdout.

The regular expression for selecting the required namespaces to be monitored in the cluster.

If you require to monitor multiple namespaces, separate the namespaces using | without spaces.

If you are using Target Allocator, you must specify all the namespaces that you require to monitor. Target Allocator will auto-allocate these Namespaces to individual Cluster Agent replicas.

See Edit Namespaces.

The name of the pod priority class, which is used in the pod specification to set the priority.

clusterAgent.securityContext.runAsGroup

If you configured the application container as a non-root user, provide the groupId (GID) of the corresponding group.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsGroup that is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

Cluster Agent image contains a group with GID 9001.

Optional

clusterAgent.securityContext.runAsUser

If you configured the application container as a non-root user, it provides the userId (UID) of the corresponding user.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsUserthat is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

Cluster Agent image contains a user with UID 9001.

Optional

To control if a process can get more privileges than its parent process. The value is true when the container runs as:

• Privileged container
• CAP_SYS_ADMIN

To add or remove POSIX capabilities from the running containers. This uses the default set of capabilities during container runtime.

To run container in privileged mode, which is equivalent to root on the host.

The type of proc mount to use for the containers.

To specify if this container has a read-only root filesystem.

To specify if the container must run as a non-root user.

If the value is true, the Kubelet validates the image at runtime to ensure that the container fails to start when run as root. If this parameter is not specified or if the value is false, there is no validation.

To apply the SELinux context to the container. If this parameter is not specified, the container runtime allocates a random SELinux context for each container.

To specify the seccomp options used by the container. If seccomp options are specified at both the pod and container level, the container options override the pod options.

To specify Windows-specific options for every container.

Adds any required pod labels to the Cluster Agent pod. These labels are also added to the deployment of Cluster Agent.

The Agent pod runs on the node that includes the specified key-value pair within its labels property. See nodeSelector.

Requests and limits of CPU and memory resources for the Cluster Agent.

An array of tolerations required for the pod. See Taint and Tolerations.

• Regular expressions for pod names
• Pod labels

Blocklisting or allowlisting by name takes preference over blocklisting or allowlisting by labels. For example, if you have the podFilter as:

podFilter:

blocklistedLabels: - release: v1

allowlistedNames: - ^podname

This blocks all the pods which have the label 'release=v1 ' except for the ones which have the names starting with 'podname'.

• When a pod is listed as allowed by name and blocked by name, it will be allowlisted.
• When a pod is listed as allowed by a label and blocked by a label, it will be allowlisted.

Enables the use of auto allocation of namespaces to available Cluster Agent replicas. This is disabled by default. To enable this property, set enabled to true.

For information about Target Allocator, see Target Allocator.

The number of cluster Agent replicas. If Target Allocator is enabled, the default value is 3. Set the number of replicas based on your requirements. To decide how many replicas are required, see Cluster Agent Requirements and Supported Environments.

This is required when targetAllocator.enabled is set to true.

The profile to be used. Currently only the Default profile is available. The Default profile uses the 1550mi memory and 3750m CPU to monitor 2500 pods.

Required when auto-scaling is enabled.

Specify the time in seconds after which Target Allocator can scale down the replicas.

Scale-down may result in the metrics drop. By default, this parameter is disabled.

Adds any required pod labels to the pod. These labels are also added to the deployment of Target Allocator.

The Target Allocator pod runs on the node that includes the specified key-value pair within its labels property. See nodeSelector.

Requests and limits of CPU and memory resources for the Target Allocator.

An array of tolerations required for the pod. See Taint and Tolerations.

Image pull policy for Target Allocator.

Credential file used to authenticate when pulling images from your private Docker registry or repository. Based on your Docker registry configuration, you may need to create a secret file for the Splunk AppDynamics Operator to use when pulling the image for the Target Allocator, which is the same as Cluster Agent image. See Create a Secret by providing credentials on the command line.

The name of the pod priority class, which is used in the pod specification to set the priority.

The Target Allocator pod runs on the node that includes the specified key-value pair within its labels property. See nodeSelector.

An array of tolerations required for the pod. See Taint and Tolerations.

Requests and limits of CPU and memory resources for the Cluster Agent.

targetAllocatorPod.securityContext

You can include the following parameters under securityContext:

runAsGroup: If you configured the application container as a non-root user, provide the groupId of the corresponding group.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsGroupthat is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

runAsUser: If you configured the application container as a non-root user, it provides the userId of the corresponding user.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsUserthat is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

allowPrivilegeEscalation: To control if a process can get more privileges than its parent process. The value is true when the container runs as:

• Privileged container
• CAP_SYS_ADMIN

If you do not set this parameter, the helm uses the default value as true.

privileged: To run container in privileged mode, which is equivalent to root on the host.

If you do not set this parameter, the helm uses the default value as true.

If the value is true, the Kubelet validates the image at runtime to ensure that the container fails to start when run as root. If this parameter is not specified or if the value is false, there is no validation.