mirror of https://github.com/k3s-io/k3s
Salt: re-remove comment block
It had been removed in upstream, but had been kept by mistake here.pull/6/head
parent
600a0d6fe7
commit
25007421ba
|
@ -41,19 +41,6 @@ master-docker-image-tags:
|
|||
- group: root
|
||||
- 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:
|
||||
service.running:
|
||||
- enable: True
|
||||
|
|
Loading…
Reference in New Issue