From 0d2f587cea5f83a66e2f5a87fe24f2b7bf94e9e6 Mon Sep 17 00:00:00 2001 From: Justin Santa Barbara Date: Tue, 16 Jun 2015 09:18:23 -0400 Subject: [PATCH] Minor typos in cluster/addons/README.md --- cluster/addons/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cluster/addons/README.md b/cluster/addons/README.md index b374d89a203..80301cdc7b1 100644 --- a/cluster/addons/README.md +++ b/cluster/addons/README.md @@ -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 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). Each add-on must specify the following label: ````kubernetes.io/cluster-service: true````. Yaml files that do not define this label will be ignored. @@ -32,7 +32,7 @@ of: 1. Creating objects from new manifests 1. This is done for manifests that do not correspond to existing API objects 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 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