This page is for administrators who have deployed Splunk AppDynamics collectors onto their Kubernetes® clusters.
Change kubectl Context (Connect kubectl to Target Cluster)
If you manage more than one Kubernetes cluster, follow these steps to switch the context of kubectl to any target Kubernetes cluster:
Log into the computer that runs kubectl.
List the clusters (“contexts”) that kubectl knows about:
kubectl config get-contexts
BASH
Sample output:
CURRENT NAME CLUSTER ...
* admin@cluster1.mydomain.io cluster1.mydomain.io ...
admin@cluster2.mydomain.io cluster2.mydomain.io ...
CODE
Connect kubectl to your cluster, using its value in the NAME column in the output of the previous command:
kubectl config use-context <context-name>
BASH
For example,
kubectl config use-context admin@cluster2.mydomain.io
BASH
Confirm that kubectl is now connected to the right cluster:
kubectl config current-context
BASH
Sample output:
admin@cluster2.mydomain.io
CODE
Get Container Name
To find the container name, run the command kubectl describe pod <pod-name>. This command lists the names of all containers on the pod named <pod-name>.
kubectl describe pod <pod-name>
BASH
Get Configuration Values
Run the helm get values command to retrieve the values from your cluster, where <release-name> is the name you gave to your deployment of the Helm chart you specify:
helm get values <release-name> -n appdynamics
BASH
Get Deployment (Release) Name
The release name is in the NAME column of the output of the helm ls command.
Get Pod Configuration
kubectl describe pod
BASH
or
kubectl get pod -o yaml
BASH
Get Pod Logs
kubectl -n appdynamics logs <pod-name>
BASH
or
kubectl -n appdynamics logs <pod-name> -f
BASH
where -f means "follow", to configure the logs to be streamed.
List Running Pods
kubectl get pods -n appdynamics
BASH
OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.