diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-02-09 09:38:51 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-09 09:38:51 -0800 |
| commit | a21e06eb7df838452ec506e8417ac1727e688aad (patch) | |
| tree | e38a392bcb134fbd44e458f7af0ce957cd3ea247 /contributors | |
| parent | e4b062309fd2696eb4c5b1dab4e9e7077b198f77 (diff) | |
| parent | 63401e3d414a763901c54ddd3e26c45c8d4d9874 (diff) | |
Merge pull request #1772 from lijianfeng1993/fix_duplication_problem_2
Fix duplication problem in self-hosted-kubernetes.md
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/design-proposals/cluster-lifecycle/self-hosted-kubernetes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/cluster-lifecycle/self-hosted-kubernetes.md b/contributors/design-proposals/cluster-lifecycle/self-hosted-kubernetes.md index 9152f251..de13b012 100644 --- a/contributors/design-proposals/cluster-lifecycle/self-hosted-kubernetes.md +++ b/contributors/design-proposals/cluster-lifecycle/self-hosted-kubernetes.md @@ -58,7 +58,7 @@ This process has a number of moving parts. Most notably the hand off of control 1) The self-hosted Kubelet is in a precarious position as there is no one around to restart the process if it crashes. The high level is that the system init system will watch for the Kubelet POSIX lock and start the system Kubelet if the lock is missing. Once the system Kubelet starts it will launch the self-hosted Kubelet. -2) Recovering from reboots of single-master installations is a challenge as the Kubelet won't have an API server to talk to to restart the self-hosted components. We are solving this today with "[user space checkpointing](https://github.com/kubernetes-incubator/bootkube/tree/master/cmd/checkpoint#checkpoint)" container in the Kubelet pod that will periodically check the pod manifests and persist them to the static pod manifest directory. Longer term we would like for the kubelet to be able to checkpoint itself without external code. +2) Recovering from reboots of single-master installations is a challenge as the Kubelet won't have an API server to talk to restart the self-hosted components. We are solving this today with "[user space checkpointing](https://github.com/kubernetes-incubator/bootkube/tree/master/cmd/checkpoint#checkpoint)" container in the Kubelet pod that will periodically check the pod manifests and persist them to the static pod manifest directory. Longer term we would like for the kubelet to be able to checkpoint itself without external code. ## Long Term Goals |