Skip to content

Agent on Kubernetes

kubectl

The following steps assume that you have the Kubectl command installed on the machine from where you are performing the installation and that your KUBECONFIG environment variable is correctly set for your target Kubernetes cluster.

Kubernetes Namepsaces

Where you see in the below instructions should be replaced with the value of the namespace within which you want to deploy the Enterprise Session Monitor Server. This could be the same namespace as your SAS® Viya deployment, or another namespace.

Cluster-wide Deployments

  1. Remove the Agent Daemon Set: kubectl delete daemonset sas-enterprise-session-monitor-agent -n <NAMESPACE>
  2. Remove the Agent Cluster Role Binding: kubectl delete cluseterrolebinding sas-enterprise-session-monitor -n <NAMESPACE>
  3. Remove the Agent Cluster Role: kubectl delete clusterrole sas-enterprise-session-monitor -n <NAMESPACE>
  4. Remove the Service Account: kubectl delete serviceaccount sas-enterprise-session-monitor -n <NAMESPACE>
  5. Remove the Priority Class: kubectl delete priorityclass sas-enterprise-session-monitor -n <NAMESPACE>

Namespaced Deployments

  1. Remove the Agent Daemon Set: kubectl delete daemonset sas-enterprise-session-monitor-agent -n <NAMESPACE>
  2. Remove the Agent Role Binding: kubectl delete rolebinding sas-enterprise-session-monitor -n <NAMESPACE>
  3. Remove the Agent Role: kubectl delete role sas-enterprise-session-monitor -n <NAMESPACE>
  4. Remove the Service Account: kubectl delete serviceaccount sas-enterprise-session-monitor -n <NAMESPACE>
  5. Remove the Priority Class: kubectl delete priorityclass sas-enterprise-session-monitor -n <NAMESPACE>
Last update: July 20, 2023
Created: April 24, 2023