summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrandon Philips <brandon.philips@coreos.com>2017-01-17 09:32:35 -0800
committerBrandon Philips <brandon.philips@coreos.com>2017-01-17 09:32:35 -0800
commit916dfa89f67a2057218c24a3df632d5e1b2811f0 (patch)
tree3828893bc6583e032010ae8acbbd8de22b66b35c
parentde711ac20424e5a847227c28ee0675eb7e3213a1 (diff)
design-proposals: note on kubelet exit-on-lock-contention
From https://kubernetes.io/docs/admin/kubelet/
-rw-r--r--contributors/design-proposals/self-hosted-kubernetes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/self-hosted-kubernetes.md b/contributors/design-proposals/self-hosted-kubernetes.md
index bc80f58a..c10d1a2e 100644
--- a/contributors/design-proposals/self-hosted-kubernetes.md
+++ b/contributors/design-proposals/self-hosted-kubernetes.md
@@ -43,7 +43,7 @@ Today, the first component of the installation of a self-hosted cluster is [`boo
Note: In the future this temporary control plane may be replaced with a kubelet API that will enable injection of this state directly into the kubelet without a temporary Kubernetes API server.
-At the end of this process the bootkube can be shut down and the system kubelet will coordinate, through a POSIX lock, to let the self-hosted kubelet take over lifecycle and management of the control plane components. The final cluster state looks like this:
+At the end of this process the bootkube can be shut down and the system kubelet will coordinate, through a POSIX lock (see `kubelet --exit-on-lock-contention`), to let the self-hosted kubelet take over lifecycle and management of the control plane components. The final cluster state looks like this:
![](self-hosted-final-cluster.png)