-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.example.yaml
More file actions
37 lines (32 loc) · 1.3 KB
/
config.example.yaml
File metadata and controls
37 lines (32 loc) · 1.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# Vigil Controller Configuration
# Copy to config.local.yaml for local development (gitignored).
# The taint key to watch for and remove
taintKey: "node.nextdoor.com/initializing"
# The taint effect to match
taintEffect: "NoSchedule"
# All known temporary startup taint keys used in the cluster.
#
# Vigil only removes the taint specified by taintKey above. However, new nodes
# often have additional temporary taints set by other controllers (CSI drivers,
# CNI plugins, etc.). Those taints are removed by their respective controllers,
# not by Vigil.
#
# This list is used only for DaemonSet discovery: Vigil strips these taints
# before evaluating which DaemonSets should run on a node in steady state.
# Without this, DaemonSets that don't tolerate these temporary taints would be
# incorrectly excluded from the expected set.
#
# Must include taintKey itself plus any other startup taints in the cluster.
knownStartupTaintKeys:
- "node.nextdoor.com/initializing"
- "cni.istio.io/not-ready"
- "ebs.csi.aws.com/agent-not-ready"
- "efs.csi.aws.com/agent-not-ready"
# Maximum time to wait before removing taint anyway (seconds)
timeoutSeconds: 120
# DaemonSets to exclude from readiness checks
excludeDaemonSets:
# Exclude by explicit namespace/name
byName: []
# - namespace: kube-system
# name: slow-daemonset