fix typo in cluster

cluster/addons/fluentd-elasticsearch/es-image/elasticsearch_logging_discovery.go

@@ -86,7 +86,7 @@ func main() {
 		serviceName = "elasticsearch-logging"
 	}
 
-	// Look for endpoints associated with the Elasticsearch loggging service.
+	// Look for endpoints associated with the Elasticsearch logging service.
 	// First wait for the service to become available.
 	for t := time.Now(); time.Since(t) < 5*time.Minute; time.Sleep(10 * time.Second) {
 		elasticsearch, err = client.Core().Services(namespace).Get(serviceName, metav1.GetOptions{})

cluster/common.sh

@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# Common utilites for kube-up/kube-down
+# Common utilities for kube-up/kube-down
 
 set -o errexit
 set -o nounset

cluster/gce/addons/podsecuritypolicies/unprivileged-addon.yaml

@@ -3,7 +3,7 @@ kind: PodSecurityPolicy
 metadata:
   name: gce.unprivileged-addon
   annotations:
-    kubernetes.io/description: 'This policy grants the minimum ammount of
+    kubernetes.io/description: 'This policy grants the minimum amount of
       privilege necessary to run non-privileged kube-system pods. This policy is
       not intended for use outside of kube-system, and may include further
       restrictions in the future.'

cluster/gce/config-default.sh

@@ -39,7 +39,7 @@ NODE_DISK_SIZE=${NODE_DISK_SIZE:-100GB}
 NODE_LOCAL_SSDS=${NODE_LOCAL_SSDS:-0}
 # An extension to local SSDs allowing users to specify block/fs and SCSI/NVMe devices
 # Format of this variable will be "#,scsi/nvme,block/fs" you can specify multiple
-# configurations by seperating them by a semi-colon ex. "2,scsi,fs;1,nvme,block"
+# configurations by separating them by a semi-colon ex. "2,scsi,fs;1,nvme,block"
 # is a request for 2 SCSI formatted and mounted SSDs and 1 NVMe block device SSD.
 NODE_LOCAL_SSDS_EXT=${NODE_LOCAL_SSDS_EXT:-}
 # Accelerators to be attached to each node. Format "type=<accelerator-type>,count=<accelerator-count>"

cluster/gce/config-test.sh

@@ -39,7 +39,7 @@ NODE_DISK_SIZE=${NODE_DISK_SIZE:-100GB}
 NODE_LOCAL_SSDS=${NODE_LOCAL_SSDS:-0}
 # An extension to local SSDs allowing users to specify block/fs and SCSI/NVMe devices
 # Format of this variable will be "#,scsi/nvme,block/fs" you can specify multiple
-# configurations by seperating them by a semi-colon ex. "2,scsi,fs;1,nvme,block"
+# configurations by separating them by a semi-colon ex. "2,scsi,fs;1,nvme,block"
 # is a request for 2 SCSI formatted and mounted SSDs and 1 NVMe block device SSD.
 NODE_LOCAL_SSDS_EXT=${NODE_LOCAL_SSDS_EXT:-}
 NODE_ACCELERATORS=${NODE_ACCELERATORS:-""}

cluster/gce/manifests/glbc.manifest

@@ -34,7 +34,7 @@ spec:
       name: logfile
       readOnly: false
     resources:
-      # Request is set to accomodate this pod alongside the other
+      # Request is set to accommodate this pod alongside the other
       # master components on a single core master.
       # TODO: Make resource requirements depend on the size of the cluster
       requests:

cluster/gce/upgrade.sh

@@ -40,7 +40,7 @@ function usage() {
   echo "  -N:  Upgrade nodes only"
   echo "  -P:  Node upgrade prerequisites only (create a new instance template)"
   echo "  -c:  Upgrade NODE_UPGRADE_PARALLELISM nodes in parallel (default=1) within a single instance group. The MIGs themselves are dealt serially."
-  echo "  -o:  Use os distro sepcified in KUBE_NODE_OS_DISTRIBUTION for new nodes. Options include 'debian' or 'gci'"
+  echo "  -o:  Use os distro specified in KUBE_NODE_OS_DISTRIBUTION for new nodes. Options include 'debian' or 'gci'"
   echo "  -l:  Use local(dev) binaries. This is only supported for master upgrades."
   echo ""
   echo '  Version number or publication is either a proper version number'

cluster/images/etcd-version-monitor/README.md

@@ -9,7 +9,7 @@ For etcd 3.1+, the
 [go-grpc-prometheus](https://github.com/grpc-ecosystem/go-grpc-prometheus)
 metrics format, which backward incompatibly replaces the 3.0 legacy grpc metric
 format, is exposed in both the 3.1 format and in the 3.0. This preserves
-backward compatiblity.
+backward compatibility.
 
 For etcd 3.1+, the `--metrics=extensive` must be set on etcd for grpc request
 latency metrics (`etcd_grpc_unary_requests_duration_seconds`) to be exposed.

cluster/juju/layers/kubernetes-master/actions/create-rbd-pv

@@ -60,7 +60,7 @@ def main():
     if not validate_space(context['RBD_SIZE']):
         return
 
-    # Ensure our paramters match
+    # Ensure our parameters match
     param_validation = validate_parameters(context['RBD_NAME'],
                                            context['RBD_FS'],
                                            context['PV_MODE'])

cluster/juju/layers/kubernetes-worker/reactive/kubernetes_worker.py

@@ -739,7 +739,7 @@ def kubectl(*args):
 
 
 def kubectl_success(*args):
-    ''' Runs kubectl with the given args. Returns True if succesful, False if
+    ''' Runs kubectl with the given args. Returns True if successful, False if
     not. '''
     try:
         kubectl(*args)

cluster/restore-from-backup.sh

@@ -23,7 +23,7 @@
 #   b) in case of etcd3
 #      $ etcdctl --endpoints=<address> snapshot save
 #      produced .db file
-# - version.txt file is in the current directy (if it isn't it will be
+# - version.txt file is in the current directory (if it isn't it will be
 #     defaulted to "2.2.1/etcd2"). Based on this file, the script will
 #     decide to which version we are restoring (procedures are different
 #     for etcd2 and etcd3).