mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-27 20:42:58 +00:00
Salt: re-remove comment block
It had been removed in upstream, but had been kept by mistake here.
This commit is contained in:
parent
600a0d6fe7
commit
25007421ba
@ -41,19 +41,6 @@ master-docker-image-tags:
|
|||||||
- group: root
|
- group: root
|
||||||
- mode: 755
|
- mode: 755
|
||||||
|
|
||||||
# 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
|
||||||
|
Loading…
Reference in New Issue
Block a user