Master component and kubelet container upgrade fixes

* Fixes an issue where apiserver and friends (controller manager, scheduler) were prevented from restarting after manifests/secrets are changed. This occurred when a replaced kubelet doesn't reconcile new master manifests, which caused old master component versions to linger during deployment. In my case this was causing upgrades from k8s 1.6/1.7 -> k8s 1.8 to fail
* Improves transitions from kubelet container to host kubelet by preventing issues where kubelet container reappeared during the deployment
This commit is contained in:
Chad Swenson
2017-11-08 01:40:33 -06:00
parent 8b2bec700a
commit e9f795c5ce
4 changed files with 47 additions and 7 deletions

View File

@@ -3,7 +3,7 @@
template:
src: manifests/kube-apiserver.manifest.j2
dest: "{{ kube_manifest_dir }}/kube-apiserver.manifest"
notify: Master | wait for the apiserver to be running
notify: Master | Restart apiserver
tags:
- kube-apiserver
@@ -20,7 +20,7 @@
template:
src: manifests/kube-scheduler.manifest.j2
dest: "{{ kube_manifest_dir }}/kube-scheduler.manifest"
notify: Master | wait for kube-scheduler
notify: Master | Restart kube-scheduler
tags:
- kube-scheduler
@@ -35,6 +35,6 @@
template:
src: manifests/kube-controller-manager.manifest.j2
dest: "{{ kube_manifest_dir }}/kube-controller-manager.manifest"
notify: Master | wait for kube-controller-manager
notify: Master | Restart kube-controller-manager
tags:
- kube-controller-manager