mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-27 05:27:21 +00:00
Merge pull request #10328 from dchen1107/cleanup
Add dependencies on docker and kubelet service when copying master co…
This commit is contained in:
commit
d2334d60c8
@ -22,6 +22,19 @@
|
|||||||
- mode: 644
|
- mode: 644
|
||||||
|
|
||||||
# Copy kube-apiserver manifest to manifests folder for kubelet.
|
# Copy kube-apiserver manifest to manifests folder for kubelet.
|
||||||
|
# Current containervm image by default has both docker and kubelet
|
||||||
|
# running. But during cluster creation stage, docker and kubelet
|
||||||
|
# could be overwritten completely, or restarted due to flag changes.
|
||||||
|
# The ordering of salt states for service docker, kubelet and
|
||||||
|
# master-addon below is very important to avoid the race between
|
||||||
|
# salt restart docker or kubelet and kubelet start master components.
|
||||||
|
# Without the ordering of salt states, when gce instance boot up,
|
||||||
|
# configure-vm.sh will run and download the release. At the end of
|
||||||
|
# boot, run-salt will installs kube-apiserver.manifest files to
|
||||||
|
# kubelet config directory before the installation of proper version
|
||||||
|
# kubelet. Please see
|
||||||
|
# https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
|
||||||
|
# for detail explanation on this very issue.
|
||||||
/etc/kubernetes/manifests/kube-apiserver.manifest:
|
/etc/kubernetes/manifests/kube-apiserver.manifest:
|
||||||
file.managed:
|
file.managed:
|
||||||
- source: salt://kube-apiserver/kube-apiserver.manifest
|
- source: salt://kube-apiserver/kube-apiserver.manifest
|
||||||
@ -31,6 +44,9 @@
|
|||||||
- mode: 644
|
- mode: 644
|
||||||
- makedirs: true
|
- makedirs: true
|
||||||
- dir_mode: 755
|
- dir_mode: 755
|
||||||
|
- require:
|
||||||
|
- service: docker
|
||||||
|
- service: kubelet
|
||||||
|
|
||||||
#stop legacy kube-apiserver service
|
#stop legacy kube-apiserver service
|
||||||
stop_kube-apiserver:
|
stop_kube-apiserver:
|
||||||
|
@ -1,3 +1,9 @@
|
|||||||
|
# Copy kube-controller-manager manifest to manifests folder for kubelet.
|
||||||
|
# The ordering of salt states for service docker, kubelet and
|
||||||
|
# master-addon below is very important to avoid the race between
|
||||||
|
# salt restart docker or kubelet and kubelet start master components.
|
||||||
|
# Please see https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
|
||||||
|
# for detail explanation on this very issue.
|
||||||
/etc/kubernetes/manifests/kube-controller-manager.manifest:
|
/etc/kubernetes/manifests/kube-controller-manager.manifest:
|
||||||
file.managed:
|
file.managed:
|
||||||
- source: salt://kube-controller-manager/kube-controller-manager.manifest
|
- source: salt://kube-controller-manager/kube-controller-manager.manifest
|
||||||
@ -7,6 +13,9 @@
|
|||||||
- mode: 644
|
- mode: 644
|
||||||
- makedirs: true
|
- makedirs: true
|
||||||
- dir_mode: 755
|
- dir_mode: 755
|
||||||
|
- require:
|
||||||
|
- service: docker
|
||||||
|
- service: kubelet
|
||||||
|
|
||||||
/var/log/kube-controller-manager.log:
|
/var/log/kube-controller-manager.log:
|
||||||
file.managed:
|
file.managed:
|
||||||
|
@ -37,26 +37,10 @@ master-docker-image-tags:
|
|||||||
file.touch:
|
file.touch:
|
||||||
- name: /srv/pillar/docker-images.sls
|
- name: /srv/pillar/docker-images.sls
|
||||||
|
|
||||||
# Current containervm image by default has both docker and kubelet
|
|
||||||
# running. But during cluster creation stage, docker and kubelet
|
|
||||||
# could be overwritten completely, or restarted due to flag changes.
|
|
||||||
# The ordering of salt states for service docker, kubelet and
|
|
||||||
# master-addon below is very important to avoid the race between
|
|
||||||
# salt restart docker or kubelet and kubelet start master components.
|
|
||||||
# Without the ordering of salt states, when gce instance boot up,
|
|
||||||
# configure-vm.sh will run and download the release. At the end of
|
|
||||||
# boot, run-salt will run kube-master-addons service which installs
|
|
||||||
# master component manifest files to kubelet config directory before
|
|
||||||
# the installation of proper version kubelet. Please see
|
|
||||||
# https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
|
|
||||||
# for detail explanation on this very issue.
|
|
||||||
kube-master-addons:
|
kube-master-addons:
|
||||||
service.running:
|
service.running:
|
||||||
- enable: True
|
- enable: True
|
||||||
- restart: True
|
- restart: True
|
||||||
- require:
|
|
||||||
- service: docker
|
|
||||||
- service: kubelet
|
|
||||||
- watch:
|
- watch:
|
||||||
- file: master-docker-image-tags
|
- file: master-docker-image-tags
|
||||||
- file: /etc/kubernetes/kube-master-addons.sh
|
- file: /etc/kubernetes/kube-master-addons.sh
|
||||||
|
@ -1,4 +1,9 @@
|
|||||||
# Copy kube-scheduler manifest to manifests folder for kubelet.
|
# Copy kube-scheduler manifest to manifests folder for kubelet.
|
||||||
|
# The ordering of salt states for service docker, kubelet and
|
||||||
|
# master-addon below is very important to avoid the race between
|
||||||
|
# salt restart docker or kubelet and kubelet start master components.
|
||||||
|
# Please see https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
|
||||||
|
# for detail explanation on this very issue.
|
||||||
/etc/kubernetes/manifests/kube-scheduler.manifest:
|
/etc/kubernetes/manifests/kube-scheduler.manifest:
|
||||||
file.managed:
|
file.managed:
|
||||||
- source: salt://kube-scheduler/kube-scheduler.manifest
|
- source: salt://kube-scheduler/kube-scheduler.manifest
|
||||||
@ -8,6 +13,9 @@
|
|||||||
- mode: 644
|
- mode: 644
|
||||||
- makedirs: true
|
- makedirs: true
|
||||||
- dir_mode: 755
|
- dir_mode: 755
|
||||||
|
- require:
|
||||||
|
- service: docker
|
||||||
|
- service: kubelet
|
||||||
|
|
||||||
/var/log/kube-scheduler.log:
|
/var/log/kube-scheduler.log:
|
||||||
file.managed:
|
file.managed:
|
||||||
|
Loading…
Reference in New Issue
Block a user