Allow the DaemonSet to schedule ussing affinity rules (#17180)

Heavily inspired by
https://github.com/helm/charts/blob/master/stable/signalsciences.

Signed-off-by: Thiago Caiubi <thiago.caiubi@gmail.com>
This commit is contained in:
Thiago Caiubi
2019-09-17 07:02:26 -07:00
committed by Kubernetes Prow Robot
parent 4d80c40c30
commit f0ade143a2
5 changed files with 15 additions and 1 deletions
+6
View File
@@ -3,6 +3,12 @@
This file documents all notable changes to Sysdig Helm Chart. The release
numbering uses [semantic versioning](http://semver.org).
## v1.4.16
### Minor changes
* Allow the DaemonSet to schedule using affinity rules
## v1.4.15
### Minor changes
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: sysdig
version: 1.4.15
version: 1.4.16
appVersion: 0.92.1
description: Sysdig Monitor and Secure agent
keywords:
+1
View File
@@ -52,6 +52,7 @@ The following table lists the configurable parameters of the Sysdig chart and th
| `serviceAccount.create` | Create serviceAccount | `true` |
| `serviceAccount.name` | Use this value as serviceAccountName | ` ` |
| `daemonset.updateStrategy.type` | The updateStrategy for updating the daemonset | `RollingUpdate` |
| `daemonset.affinity` | Node affinities | `nil` |
| `ebpf.enabled` | Enable eBPF support for Sysdig instead of `sysdig-probe` kernel module | `false` |
| `ebpf.settings.mountEtcVolume` | Needed to detect which kernel version are running in Google COS | `true` |
| `sysdig.accessKey` | Your Sysdig Monitor Access Key | `Nil` You must provide your own key |
+4
View File
@@ -26,6 +26,10 @@ spec:
dnsPolicy: ClusterFirstWithHostNet
hostPID: true
terminationGracePeriodSeconds: 5
{{- if .Values.daemonset.affinity }}
affinity:
{{ toYaml .Values.daemonset.affinity | indent 8 }}
{{- end }}
{{- if .Values.image.pullSecrets }}
imagePullSecrets:
{{ toYaml .Values.image.pullSecrets | indent 8 }}
+3
View File
@@ -45,6 +45,9 @@ daemonset:
type: RollingUpdate
## Extra environment variables that will be pass onto deployment pods
env: {}
## Allow the DaemonSet to schedule using affinity rules
# Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
# affinity: {}
# If is behind a proxy you can set the proxy server
proxy: