- Ensure all sysdig pods are 1/1 Running state.
- Double check the largest image size to make sure a new larger image is not encountered.
- If a new and larger image is encountered, we may need to tune the runtime scanner to accommodate the larger size.
- You can also watch for log messages with "too" that say image scans are being skipped due to size.
- Grep all of the agent pod logs for "Error," and ensure there are no recurring errors of concern.
- Grep all of the agent pod logs for "POLICIES_V2". You should see something like "Received command 22 (POLICIES_V2)" This signifies that the pod is up and running successfully.
- Grep all of the agent node analyzer pod logs for ""level":"error"" and ensure there are no recurring errors of concern.
- Sometimes you will see recurring errors if a scan is attempted for an application pod that has not come up or is failing.
- Grep all of the agent node analyzer pods logs for ""message":"startup sleep"". This signifies that the pod is up and running successfully.
helm repo add sysdig https://charts.sysdig.com --force-update
helm install sysdig-agent \
--namespace <namespace> \
--set global.sysdig.accessKey=<access-key> \
...
-f example-values-file.yaml \
sysdig/sysdig-deploy
- Refer to these docs for additional params: Helm Upgrade Docs
- helm upgrade --force to override values
helm upgrade sysdig-agent \
--namespace <namespace> \
--set global.sysdig.accessKey=<access key> \
--set agent.image.tag=<version> \
--set nodeAnalyzer.nodeAnalyzer.runtimeScanner.image.tag=<version> \
...
-f example-values-file.yaml \
sysdig/sysdig-deploy
helm upgrade --force sysdig-agent \
--namespace <namespace> \
--set global.sysdig.accessKey=<access key> \
...
-f example-values-file.yaml \
sysdig/sysdig-deploy
helm list --namespace <namespace>
helm status sysdig-agent --namespace <namespace>
helm uninstall sysdig-agent --namespace <namespace>
helm delete sysdig-agent --namespace <namespace>