Néstor Salcedaandk8s-ci-robot
402aeebfe8
* [stable/sysdig] Update to latest agent version * Run Sysdig Agent as [daemonset v2.0](https://github.com/draios/sysdig-cloud-scripts/blob/master/agent_deploy/kubernetes/sysdig-agent-daemonset-v2.yaml). * Fix value's naming in order to follow [best practices](https://docs.helm.sh/chart_best_practices/#naming-conventions). * Use a secure.enabled flag for enabling Sysdig Secure. * Allow rbac resource creation or use existing serviceAccountName. * Use required function for retrieving sysdig.accessKey. This ensures that key is present. * Add a Changelog * Use GitHub accounts instead of real names for making CI pass * Fix version number as a string * Add OWNERS file * Separate rbac and serviceAccount Follow RBAC best practices: https://github.com/kubernetes/helm/blob/master/docs/chart_best_practices/rbac.md * Fix namespace issues in cluster role binding
Sysdig
Sysdig is a unified platform for container and microservices monitoring, troubleshooting, security and forensics. Sysdig platform has been built on top of Sysdig tool and Sysdig Inspect open-source technologies.
Introduction
This chart adds the Sysdig agent for Sysdig Monitor and Sysdig Secure to all nodes in your cluster via a DaemonSet.
Prerequisites
- Kubernetes 1.2+ with Beta APIs enabled
Installing the Chart
To install the chart with the release name my-release, retrieve your Sysdig Monitor Access Key from your Account Settings and run:
$ helm install --name my-release \
--set sysdig.accessKey=YOUR-KEY-HERE stable/sysdig
After a few seconds, you should see hosts and containers appearing in Sysdig Monitor and Sysdig Secure.
Tip
: List all releases using
helm list
Uninstalling the Chart
To uninstall/delete the my-release deployment:
$ helm delete my-release
Tip
: Use helm delete --purge my-release to completely remove the release from Helm internal storage
The command removes all the Kubernetes components associated with the chart and deletes the release.
Configuration
The following table lists the configurable parameters of the Sysdig chart and their default values.
| Parameter | Description | Default |
|---|---|---|
image.repository |
The image repository to pull from | sysdig/agent |
image.tag |
The image tag to pull | latest |
image.pullPolicy |
The Image pull policy | Always |
rbac.create |
If true, create & use RBAC resources | true |
serviceAccount.create |
Create serviceAccount | true |
serviceAccount.name |
Use this value as serviceAccountName | |
sysdig.accessKey |
Your Sysdig Monitor Access Key | Nil You must provide your own key |
sysdig.settings |
Settings for agent's configuration file | {} |
secure.enabled |
Enable Sysdig Secure | false |
tolerations |
The tolerations for scheduling | node-role.kubernetes.io/master:NoSchedule |
Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,
$ helm install --name my-release \
--set sysdig.accessKey=YOUR-KEY-HERE,sysdig.AgentTags="role:webserver,location:europe" \
stable/sysdig
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml stable/sysdig
Tip
: You can use the default values.yaml