Small typos fixed
This commit is contained in:
@@ -14,7 +14,7 @@ various mechanisms (primarily through the apiserver) and ensures that the contai
|
|||||||
described in those PodSpecs are running and healthy. The kubelet doesn't manage
|
described in those PodSpecs are running and healthy. The kubelet doesn't manage
|
||||||
containers which were not created by Kubernetes.
|
containers which were not created by Kubernetes.
|
||||||
|
|
||||||
Other than from an PodSpec from the apiserver, there are three ways that a container
|
Other than from a PodSpec from the apiserver, there are three ways that a container
|
||||||
manifest can be provided to the Kubelet.
|
manifest can be provided to the Kubelet.
|
||||||
|
|
||||||
File: Path passed as a flag on the command line. This file is rechecked every 20
|
File: Path passed as a flag on the command line. This file is rechecked every 20
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Each critical add-on has to tolerate it,
|
|||||||
the other pods shouldn't tolerate the taint. The tain is removed once the add-on is successfully scheduled.
|
the other pods shouldn't tolerate the taint. The tain is removed once the add-on is successfully scheduled.
|
||||||
|
|
||||||
*Warning:* currently there is no guarantee which node is chosen and which pods are being killed
|
*Warning:* currently there is no guarantee which node is chosen and which pods are being killed
|
||||||
in order to schedule crical pod, so if rescheduler is enabled you pods might be occasionally
|
in order to schedule crical pods, so if rescheduler is enabled you pods might be occasionally
|
||||||
killed for this purpose.
|
killed for this purpose.
|
||||||
|
|
||||||
## Config
|
## Config
|
||||||
|
|||||||
@@ -19,7 +19,7 @@ The installation uses a tool called `kubeadm` which is part of Kubernetes.
|
|||||||
This process works with local VMs, physical servers and/or cloud servers.
|
This process works with local VMs, physical servers and/or cloud servers.
|
||||||
It is simple enough that you can easily integrate its use into your own automation (Terraform, Chef, Puppet, etc).
|
It is simple enough that you can easily integrate its use into your own automation (Terraform, Chef, Puppet, etc).
|
||||||
|
|
||||||
See the full [`kubeadm` reference](/docs/admin/kubeadm) for information on all `kubeadm` command-line flags and for advice on automating `kubeadm` itself.
|
See the full `kubeadm` [reference](/docs/admin/kubeadm) for information on all `kubeadm` command-line flags and for advice on automating `kubeadm` itself.
|
||||||
|
|
||||||
**The `kubeadm` tool is currently in alpha but please try it out and give us [feedback](/docs/getting-started-guides/kubeadm/#feedback)!
|
**The `kubeadm` tool is currently in alpha but please try it out and give us [feedback](/docs/getting-started-guides/kubeadm/#feedback)!
|
||||||
Be sure to read the [limitations](#limitations); in particular note that kubeadm doesn't have great support for
|
Be sure to read the [limitations](#limitations); in particular note that kubeadm doesn't have great support for
|
||||||
|
|||||||
Reference in New Issue
Block a user