Kubernetes
Sysdig offers the sysdig-deploy helm chart to provide you with a streamlined, repeatable deployment process that is easy to manage and scale.
For information on installing Sysdig Secure see, Install Sysdig Secure in Kubernetes.
Prerequisites
Review the Installation Requirements.
Install the following:
kubectl
- Helm
v3.6
or above
If you are not using the Quick Start Wizard for the installation command, collect the following:
For more information on agent configuration, see Configure Sysdig Agent.
Installation
Log in to Sysdig Monitor as an administrator.
Select Integrations > Sysdig Agent.
Click +Add Account and select Kubernetes Cluster.
The Helm installation method is recommended.
As prompted by the screen, enter the name of your Kubernetes cluster.
The Wizard will auto-populate a code snippet with the cluster name, along with the autodetected Sysdig Monitor endpoint and the agent access key.
Copy and run the Helm commands.
The command uses the
sysdig-deploy
chart to install the Sysdig Agent.You can also use a
values.yaml
to install the agent.helm repo add sysdig https://charts.sysdig.com helm repo update helm install sysdig-agent --namespace sysdig-agent --create-namespace \ helm install sysdig --namespace sysdig-agent \ --set global.sysdig.accessKey=<ACCESS_KEY> \ --set global.sysdig.region=<SAAS_REGION> \ --set nodeAnalyzer.enabled=false \ --set global.clusterConfig.name=<CLUSTER_NAME> \ sysdig/sysdig-deploy
## create a values.yaml file with the following: global: sysdig: accessKey: <ACCESS_KEY> region: <SAAS_REGION> clusterConfig: name: <CLUSTER_NAME> nodeAnalyzer: enabled: false ## Install by running the following: helm repo add sysdig https://charts.sysdig.com helm install -n sysdig-agent sysdig sysdig/sysdig-deploy -f values.sysdig.yaml
Alternatively, you can directly run this command, specifying the following parameters.
Options
The command above has the following options:
--namespace sysdig-agent
: Specifies that the agent should be installed in thesysdig-agent
namespace.--set global.sysdig.accessKey=<ACCESS_KEY>
: Specifies the Sysdig access key to use when connecting to the Sysdig backend. Replace<ACCESS_KEY>
with your actual access key.--set global.sysdig.region=<SAAS_REGION>
: Specifies the Sysdig region to use. Replace<SAAS_REGION>
with the region where your Sysdig account is located.For example,
us1
for US East (Virginia),us2
for US West AWS , andau1
for AP Australia. See Regions and IP Ranges for more information.--set nodeAnalyzer.nodeAnalyzer.benchmarkRunner.deploy=false
: Disables the Node Analyzer component. This is used by Secure users only.--set global.clusterConfig.name=<CLUSTER_NAME>
: Specifies the name of your Kubernetes cluster. Replace<CLUSTER_NAME>
with your actual Kubernetes cluster name.
After running these commands, the Sysdig agent should be installed and running on your Kubernetes cluster, and starts sending data to the Sysdig backend.
Platform-Specific Options
If you are using Openshift, GKE Standard, OKE, or MKE, enable eBPF with the following option:
--set agent.ebpf.enabled=true
If you are using GKE autopilot, enable the following option:
--set agent.gke.autopilot=true
Additional Options
For additional configuration options, including on-premise and proxy connection, seesysdig-deploy.
Uninstall Sysdig Agent
If the agent was installed in a Kubernetes environment, remove it by using the standard Kubernetes commands.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.