Update examples
Promote the timeout to a top-level field, timeouts can only be trusted if they are enforced by the caller, not callee.
Change the kubelet example to show how drain + restart might be achieved.
@@ -99,17 +99,18 @@ as data, the file will be a list of entries containing:
- filename
- path
- action to perform
-- action specific data (eg. the service name, timeout)
+- action specific data (eg. the service name)
+- timeout
-Example entries:
+Example (and not necessarily 100% accurate) entries:
-| File | Path | Action | Args |
-| ---- | ---- | ------ | ---- |
+| File | Path | Action | Args | Timeout |
+| ---- | ---- | ------ | ---- | ------- |
| * | /var/home/core/.ssh/ | none ||
-| kubelet.conf | /etc/kubernetes/ | none ||
-| crio.conf | /etc/crio/ | systemctl | _restart_ crio.service |
-| seccomp.json | /etc/crio/ | systemctl | _reload_ crio.service |
-| imaginary.conf | /somewhere/ | binary | /bin/my-custom-tool -q --timeout 20s |
+| kubelet.conf | /etc/kubernetes/ | binary | /bin/custom-drain-and-restart-tool -v3 | 30min |
+| crio.conf | /etc/crio/ | systemctl | _restart_ crio.service ||
+| seccomp.json | /etc/crio/ | systemctl | _reload_ crio.service ||
+| imaginary.conf | /somewhere/ | binary | /bin/my-custom-tool -q || 20s |
After the MCD writes out a configuation change, it will consult the whitelist
before deciding if a reboot is required. If the filename is present, has a
