kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

small grammar fixes in overview/components.md (#14693) 

Trival patch to fix a couple grammatical mistakes I found while going
through overview/components.md.
This commit is contained in:
Jay Pipes 2019-06-03 20:50:59 -04:00 committed by Kubernetes Prow Robot
parent 88fe150abc
commit eda841cb0a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/concepts/overview/components.md
View File

@ -18,7 +18,7 @@ deliver a functioning Kubernetes cluster.
## Master Components ## Master Components
Master components provide the cluster's control plane. Master components make global decisions about the Master components provide the cluster's control plane. Master components make global decisions about the
cluster (for example, scheduling), and detecting and responding to cluster events (starting up a new pod when a replication controller's `replicas` field is unsatisfied). cluster (for example, scheduling), and they detect and respond to cluster events (for example, starting up a new pod when a replication controller's `replicas` field is unsatisfied).
Master components can be run on any machine in the cluster. However, Master components can be run on any machine in the cluster. However,
for simplicity, set up scripts typically start all master components on for simplicity, set up scripts typically start all master components on
@ -55,7 +55,7 @@ These controllers include:
cloud-controller-manager runs cloud-provider-specific controller loops only. You must disable these controller loops in the kube-controller-manager. You can disable the controller loops by setting the `--cloud-provider` flag to `external` when starting the kube-controller-manager. cloud-controller-manager runs cloud-provider-specific controller loops only. You must disable these controller loops in the kube-controller-manager. You can disable the controller loops by setting the `--cloud-provider` flag to `external` when starting the kube-controller-manager.
cloud-controller-manager allows cloud vendors code and the Kubernetes code to evolve independent of each other. In prior releases, the core Kubernetes code was dependent upon cloud-provider-specific code for functionality. In future releases, code specific to cloud vendors should be maintained by the cloud vendor themselves, and linked to cloud-controller-manager while running Kubernetes. cloud-controller-manager allows the cloud vendor's code and the Kubernetes code to evolve independently of each other. In prior releases, the core Kubernetes code was dependent upon cloud-provider-specific code for functionality. In future releases, code specific to cloud vendors should be maintained by the cloud vendor themselves, and linked to cloud-controller-manager while running Kubernetes.
The following controllers have cloud provider dependencies: The following controllers have cloud provider dependencies: