github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-27 05:27:21 +00:00
Code Issues Projects Releases Wiki Activity

Minor typos in cluster/addons/README.md

Browse Source
This commit is contained in:
Justin Santa Barbara 2015-06-16 09:18:23 -04:00
parent a8269e38c9
commit 0d2f587cea
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cluster/addons/README.md
View File

@ -4,7 +4,7 @@ Cluster add-ons are Services and Replication Controllers (with pods) that are
shipped with the kubernetes binaries and whose update policy is also consistent shipped with the kubernetes binaries and whose update policy is also consistent
with the update of kubernetes cluster. with the update of kubernetes cluster.
On the clusterm the addons are kept in ```/etc/kubernetes/addons``` on the master node, in yaml files On the cluster the addons are kept in ```/etc/kubernetes/addons``` on the master node, in yaml files
(json is not supported at the moment). (json is not supported at the moment).
Each add-on must specify the following label: ````kubernetes.io/cluster-service: true````. Each add-on must specify the following label: ````kubernetes.io/cluster-service: true````.
Yaml files that do not define this label will be ignored. Yaml files that do not define this label will be ignored.
@ -32,7 +32,7 @@ of:
1. Creating objects from new manifests 1. Creating objects from new manifests
1. This is done for manifests that do not correspond to existing API objects 1. This is done for manifests that do not correspond to existing API objects
with the same basename with the same basename
1. Updating objects whose basename is the samem but whose versions changed. 1. Updating objects whose basename is the same, but whose versions changed.
1. The update is currently performed by removing the old object and creating 1. The update is currently performed by removing the old object and creating
the new one. In the future, rolling update of replication controllers will the new one. In the future, rolling update of replication controllers will
be implemented to keep the add-on services up and running during update of add-on be implemented to keep the add-on services up and running during update of add-on