Spelling fixes inspired by github.com/client9/misspell

api/swagger-spec/v1.json

@@ -8246,7 +8246,7 @@
         "type": "string",
         "paramType": "query",
         "name": "sinceTime",
-        "description": "An RFC3339 timestamp from which to show logs. If this value preceeds the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.",
+        "description": "An RFC3339 timestamp from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.",
         "required": false,
         "allowMultiple": false
        },
@@ -17236,7 +17236,7 @@
    },
    "v1.ServicePort": {
     "id": "v1.ServicePort",
-    "description": "ServicePort conatins information on service's port.",
+    "description": "ServicePort contains information on service's port.",
     "required": [
      "port"
     ],

build/common.sh

@@ -1562,7 +1562,7 @@ function kube::release::docker::release() {
       kube::log::status "Pushing ${binary} to ${docker_target}"
       "${docker_push_cmd[@]}" push "${docker_target}"
 
-      # If we have a amd64 docker image. Tag it without -amd64 also and push it for compability with earlier versions
+      # If we have a amd64 docker image. Tag it without -amd64 also and push it for compatibility with earlier versions
       if [[ ${arch} == "amd64" ]]; then
         local legacy_docker_target="${KUBE_DOCKER_REGISTRY}/${binary}:${KUBE_DOCKER_IMAGE_TAG}"
 

cluster/addons/cluster-loadbalancing/glbc/glbc-controller.yaml

@@ -25,7 +25,7 @@ spec:
       terminationGracePeriodSeconds: 600
       containers:
       - name: default-http-backend
-        # Any image is permissable as long as:
+        # Any image is permissible as long as:
         # 1. It serves a 404 page at /
         # 2. It serves 200 on a /healthz endpoint
         image: gcr.io/google_containers/defaultbackend:1.0

cluster/addons/registry/README.md

@@ -60,7 +60,7 @@ created independently - this is not something Kubernetes manages for you (yet).
 ### I don't want or don't have persistent storage
 
 If you are running in a place that doesn't have networked storage, or if you
-just want to kick the tires on this without commiting to it, you can easily
+just want to kick the tires on this without committing to it, you can easily
 adapt the `ReplicationController` specification below to use a simple
 `emptyDir` volume instead of a `persistentVolumeClaim`.
 

cluster/aws/util.sh

@@ -53,7 +53,7 @@ if [[ "${KUBE_OS_DISTRIBUTION}" == "ubuntu" ]]; then
   KUBE_OS_DISTRIBUTION=vivid
 fi
 
-# For GCE script compatability
+# For GCE script compatibility
 OS_DISTRIBUTION=${KUBE_OS_DISTRIBUTION}
 
 case "${KUBE_OS_DISTRIBUTION}" in

cluster/gce/coreos/kube-manifests/addons/cluster-loadbalancing/glbc/glbc-controller.yaml

@@ -25,7 +25,7 @@ spec:
       terminationGracePeriodSeconds: 600
       containers:
       - name: default-http-backend
-        # Any image is permissable as long as:
+        # Any image is permissible as long as:
         # 1. It serves a 404 page at /
         # 2. It serves 200 on a /healthz endpoint
         image: gcr.io/google_containers/defaultbackend:1.0

cluster/gce/trusty/helper.sh

@@ -18,7 +18,7 @@
 
 # The code and configuration is for running node instances on Ubuntu images.
 # The master is still on Debian. In addition, the configuration is based on
-# upstart, which is in Ubuntu upto 14.04 LTS (Trusty). Ubuntu 15.04 and above
+# upstart, which is in Ubuntu up to 14.04 LTS (Trusty). Ubuntu 15.04 and above
 # replaced upstart with systemd as the init system. Consequently, the
 # configuration cannot work on these images.
 

cluster/images/etcd/Makefile

@@ -46,14 +46,14 @@ build:
 	docker build -t ${REGISTRY}/etcd-${ARCH}:${TAG} ${TEMP_DIR}
 
 ifeq ($(ARCH),amd64)
-	# Backward compatability. TODO: deprecate this image tag
+	# Backward compatibility. TODO: deprecate this image tag
 	docker tag -f ${REGISTRY}/etcd-${ARCH}:${TAG} ${REGISTRY}/etcd:${TAG}
 endif
 
 push: build
 	gcloud docker push ${REGISTRY}/etcd-${ARCH}:${TAG}
 
-	# Backward compatability. TODO: deprecate this image tag
+	# Backward compatibility. TODO: deprecate this image tag
 ifeq ($(ARCH),amd64)
 	gcloud docker push ${REGISTRY}/etcd:${TAG}
 endif

cluster/images/hyperkube/Makefile

@@ -41,7 +41,7 @@ endif
 	cd ${TEMP_DIR} && sed -i "s/ARCH/${ARCH}/g" master-multi.json master.json kube-proxy.json
 	cd ${TEMP_DIR} && sed -i "s/BASEIMAGE/${BASEIMAGE}/g" Dockerfile
 	docker build -t ${REGISTRY}/hyperkube-${ARCH}:${VERSION} ${TEMP_DIR}
-	# Backward compatability.  TODO: deprecate this image tag
+	# Backward compatibility.  TODO: deprecate this image tag
 ifeq ($(ARCH),amd64)
 	docker tag -f ${REGISTRY}/hyperkube-${ARCH}:${VERSION} ${REGISTRY}/hyperkube:${VERSION}
 endif

cluster/juju/util.sh

@@ -128,7 +128,7 @@ function kube-down() {
 }
 
 function prepare-e2e() {
-  echo "prepare-e2e() The Juju provider does not need any preperations for e2e." 1>&2
+  echo "prepare-e2e() The Juju provider does not need any preparations for e2e." 1>&2
 }
 
 function sleep-status() {

cluster/ubuntu/reconfDocker.sh

@@ -72,6 +72,6 @@ elif [[ $1 == "ai" ]]; then
 elif [[ $1 == "a" ]]; then
   config_etcd
 else
-  echo "Another arguement is required."
+  echo "Another argument is required."
   exit 1
 fi 

cmd/kubelet/app/options/options.go

@@ -182,7 +182,7 @@ func (s *KubeletServer) AddFlags(fs *pflag.FlagSet) {
 	fs.DurationVar(&s.StreamingConnectionIdleTimeout.Duration, "streaming-connection-idle-timeout", s.StreamingConnectionIdleTimeout.Duration, "Maximum time a streaming connection can be idle before the connection is automatically closed. 0 indicates no timeout. Example: '5m'")
 	fs.DurationVar(&s.NodeStatusUpdateFrequency.Duration, "node-status-update-frequency", s.NodeStatusUpdateFrequency.Duration, "Specifies how often kubelet posts node status to master. Note: be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. Default: 10s")
 	bindableNodeLabels := util.ConfigurationMap(s.NodeLabels)
-	fs.Var(&bindableNodeLabels, "node-labels", "<Warning: Alpha feature> Labels to add when registering the node in the cluster.  Labels must are key=value pairs seperated by ','.")
+	fs.Var(&bindableNodeLabels, "node-labels", "<Warning: Alpha feature> Labels to add when registering the node in the cluster.  Labels must are key=value pairs separated by ','.")
 	fs.DurationVar(&s.ImageMinimumGCAge.Duration, "minimum-image-ttl-duration", s.ImageMinimumGCAge.Duration, "Minimum age for a unused image before it is garbage collected.  Examples: '300ms', '10s' or '2h45m'. Default: '2m'")
 	fs.IntVar(&s.ImageGCHighThresholdPercent, "image-gc-high-threshold", s.ImageGCHighThresholdPercent, "The percent of disk usage after which image garbage collection is always run. Default: 90%")
 	fs.IntVar(&s.ImageGCLowThresholdPercent, "image-gc-low-threshold", s.ImageGCLowThresholdPercent, "The percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. Default: 80%")

cmd/libs/go2idl/generator/default_package.go

@@ -20,7 +20,7 @@ import (
 	"k8s.io/kubernetes/cmd/libs/go2idl/types"
 )
 
-// DefaultPackage contains a default implentation of Package.
+// DefaultPackage contains a default implementation of Package.
 type DefaultPackage struct {
 	// Short name of package, used in the "package xxxx" line.
 	PackageName string

cmd/libs/go2idl/go-to-protobuf/protobuf/package.go

@@ -52,7 +52,7 @@ func newProtobufPackage(packagePath, packageName string, generateAll bool, omitF
 	return pkg
 }
 
-// protobufPackage contains the protobuf implentation of Package.
+// protobufPackage contains the protobuf implementation of Package.
 type protobufPackage struct {
 	// Short name of package, used in the "package xxxx" line.
 	PackageName string

contrib/mesos/pkg/executor/messages/messages.go

@@ -29,7 +29,7 @@ const (
 	TaskKilled               = "task-killed"
 	TaskLost                 = "task-lost"
 	UnmarshalTaskDataFailure = "unmarshal-task-data-failure"
-	TaskLostAck              = "task-lost-ack" // executor acknowledgement of forwarded TASK_LOST framework message
+	TaskLostAck              = "task-lost-ack" // executor acknowledgment of forwarded TASK_LOST framework message
 	Kamikaze                 = "kamikaze"
 	WrongSlaveFailure        = "pod-for-wrong-slave-failure"
 	AnnotationUpdateFailure  = "annotation-update-failure"

contrib/mesos/pkg/offers/offers.go

@@ -271,7 +271,7 @@ func (s *offerStorage) Delete(offerId string, reason metrics.OfferDeclinedReason
 				s.declineOffer(offerId, offer.Host(), reason)
 			} else {
 				// some pod has acquired this and may attempt to launch a task with it
-				// failed schedule/launch attempts are requried to Release() any claims on the offer
+				// failed schedule/launch attempts are required to Release() any claims on the offer
 
 				// TODO(jdef): not sure what a good value is here. the goal is to provide a
 				// launchTasks (driver) operation enough time to complete so that we don't end

contrib/mesos/pkg/scheduler/components/framework/framework.go

@@ -315,7 +315,7 @@ func (k *framework) Registered(drv bindings.SchedulerDriver, fid *mesos.Framewor
 }
 
 // Reregistered is called when the scheduler re-registered with the master successfully.
-// This happends when the master fails over.
+// This happens when the master fails over.
 func (k *framework) Reregistered(drv bindings.SchedulerDriver, mi *mesos.MasterInfo) {
 	log.Infof("Scheduler reregistered with the master: %v\n", mi)
 

contrib/mesos/pkg/scheduler/components/podreconciler/doc.go

@@ -14,6 +14,6 @@ See the License for the specific language governing permissions and
 limitations under the License.
 */
 
-// Package podreconciler implements pod reconcilation of pods which failed
+// Package podreconciler implements pod reconciliation of pods which failed
 // to launch, i.e. before binding by the executor took place.
 package podreconciler

contrib/mesos/pkg/scheduler/components/tasksreconciler/doc.go

@@ -14,5 +14,5 @@ See the License for the specific language governing permissions and
 limitations under the License.
 */
 
-// Package taskreconciler implement Mesos task reconcilation.
+// Package taskreconciler implement Mesos task reconciliation.
 package taskreconciler

docs/admin/admission-controllers.md

@@ -182,7 +182,7 @@ We strongly recommend `NamespaceLifecycle` over `NamespaceAutoProvision`.
 ### NamespaceLifecycle
 
 This plug-in enforces that a `Namespace` that is undergoing termination cannot have new objects created in it,
-and ensures that requests in a non-existant `Namespace` are rejected.
+and ensures that requests in a non-existent `Namespace` are rejected.
 
 A `Namespace` deletion kicks off a sequence of operations that remove all objects (pods, services, etc.) in that
 namespace.  In order to enforce integrity of that process, we strongly recommend running this plug-in.

docs/admin/kubelet.md

@@ -120,7 +120,7 @@ kubelet
       --network-plugin="": <Warning: Alpha feature> The name of the network plugin to be invoked for various events in kubelet/pod lifecycle
       --network-plugin-dir="/usr/libexec/kubernetes/kubelet-plugins/net/exec/": <Warning: Alpha feature> The full path of the directory in which to search for network plugins
       --node-ip="": IP address of the node. If set, kubelet will use this IP address for the node
-      --node-labels=: <Warning: Alpha feature> Labels to add when registering the node in the cluster.  Labels must are key=value pairs seperated by ','.
+      --node-labels=: <Warning: Alpha feature> Labels to add when registering the node in the cluster.  Labels must are key=value pairs separated by ','.
       --node-status-update-frequency=10s: Specifies how often kubelet posts node status to master. Note: be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. Default: 10s
       --non-masquerade-cidr="10.0.0.0/8": Traffic to IPs outside this range will use IP masquerade.
       --oom-score-adj=-999: The oom-score-adj value for kubelet process. Values must be within the range [-1000, 1000]
@@ -152,7 +152,7 @@ kubelet
       --volume-stats-agg-period=1m0s: Specifies interval for kubelet to calculate and cache the volume disk usage for all pods and volumes.  To disable volume calculations, set to 0.  Default: '1m'
 ```
 
-###### Auto generated by spf13/cobra on 15-Feb-2016
+###### Auto generated by spf13/cobra on 17-Feb-2016
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

docs/admin/master-node-communication.md

@@ -102,7 +102,7 @@ HTTP connections and are therefore neither authenticated nor encrypted. They
 can be run over a secure HTTPS connection by prefixing `https:` to the node,
 pod, or service name in the API URL, but they will not validate the certificate
 provided by the HTTPS endpoint nor provide client credentials so while the
-connection will by encrypted, it will not provide any guarentees of integrity.
+connection will by encrypted, it will not provide any guarantees of integrity.
 These connections **are not currently safe** to run over untrusted and/or
 public networks.
 

docs/api-reference/v1/definitions.html

@@ -5470,7 +5470,7 @@ <h3 id="_v1_finalizername">v1.FinalizerName</h3>
 <div class="sect2">
 <h3 id="_v1_serviceport">v1.ServicePort</h3>
 <div class="paragraph">
-<p>ServicePort conatins information on service&#8217;s port.</p>
+<p>ServicePort contains information on service&#8217;s port.</p>
 </div>
 <table class="tableblock frame-all grid-all" style="width:100%; ">
 <colgroup>

docs/api-reference/v1/operations.html

@@ -8196,7 +8196,7 @@ <h4 id="_parameters_59">Parameters</h4>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">QueryParameter</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">sinceTime</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">An RFC3339 timestamp from which to show logs. If this value preceeds the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">An RFC3339 timestamp from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">string</p></td>
 <td class="tableblock halign-left valign-top"></td>

docs/design/clustering/dynamic.seqdiag

@@ -15,7 +15,7 @@ seqdiag {
 
   user ->> kubelet [label="start\n- bootstrap-cluster-uri"];
   kubelet => bootstrap [label="get-master", return="returns\n- master-location\n- master-ca"];
-  kubelet ->> master [label="signCert\n- unsigned-kubelet-cert", return="retuns\n- kubelet-cert"];
+  kubelet ->> master [label="signCert\n- unsigned-kubelet-cert", return="returns\n- kubelet-cert"];
   user => master [label="getSignRequests"];
   user => master [label="approveSignRequests"];
   kubelet <<-- master [label="returns\n- kubelet-cert"];

docs/design/enhance-pluggable-policy.md

@@ -54,7 +54,7 @@ An API request has the following attributes that can be considered for authoriza
   - resourceVersion - the API version of the resource being accessed
   - resource - which resource is being accessed
     - applies only to the API endpoints, such as
-        `/api/v1beta1/pods`.  For miscelaneous endpoints, like `/version`, the kind is the empty string.
+        `/api/v1beta1/pods`.  For miscellaneous endpoints, like `/version`, the kind is the empty string.
   - resourceName - the name of the resource during a get, update, or delete action.
   - subresource - which subresource is being accessed
 

docs/design/indexed-job.md

@@ -33,18 +33,18 @@ Documentation for other releases can be found at
 ## Summary
 
 This design extends kubernetes with user-friendly support for
-running embarassingly parallel jobs.
+running embarrassingly parallel jobs.
 
 Here, *parallel* means on multiple nodes, which means multiple pods.
-By *embarassingly parallel*,  it is meant that the pods
+By *embarrassingly parallel*,  it is meant that the pods
 have no dependencies between each other.  In particular, neither
 ordering between pods nor gang scheduling are supported.
 
-Users already have two other options for running embarassingly parallel
+Users already have two other options for running embarrassingly parallel
 Jobs (described in the next section), but both have ease-of-use issues.
 
 Therefore, this document proposes extending the Job resource type to support
-a third way to run embarassingly parallel programs, with a focus on
+a third way to run embarrassingly parallel programs, with a focus on
 ease of use.
 
 This new style of Job is called an *indexed job*, because each Pod of the Job
@@ -53,7 +53,7 @@ is specialized to work on a particular *index* from a fixed length array of work
 ## Background
 
 The Kubernetes [Job](../../docs/user-guide/jobs.md) already supports
-the embarassingly parallel use case through *workqueue jobs*.
+the embarrassingly parallel use case through *workqueue jobs*.
 While [workqueue jobs](../../docs/user-guide/jobs.md#job-patterns)
  are very flexible, they can be difficult to use.
 They: (1) typically require running a message queue
@@ -242,7 +242,7 @@ In the above example:
 - `--restart=OnFailure` implies creating a job instead of replicationController.
 - Each pods command line is `/usr/local/bin/process_file $F`.
 - `--per-completion-env=` implies the jobs `.spec.completions` is set to the length of the argument array (3 in the example).
-- `--per-completion-env=F=<values>` causes env var with `F` to be available in the enviroment when the command line is evaluated.
+- `--per-completion-env=F=<values>` causes env var with `F` to be available in the environment when the command line is evaluated.
 
 How exactly this happens is discussed later in the doc: this is a sketch of the user experience.
 
@@ -269,7 +269,7 @@ Another case we do not try to handle is where the input file does not exist yet
 
 #### Multiple parameters
 
-The user may also have multiple paramters, like in [work list 2](#work-list-2).
+The user may also have multiple parameters, like in [work list 2](#work-list-2).
 One way is to just list all the command lines already expanded, one per line, in a file, like this:
 
 ```
@@ -491,7 +491,7 @@ The index-only approach:
 - requires that the user keep the *per completion parameters* in a separate storage, such as a configData or networked storage.
 - makes no changes to the JobSpec.
 - Drawback: while in separate storage, they could be mutatated, which would have unexpected effects
-- Drawback: Logic for using index to lookup paramters needs to be in the Pod.
+- Drawback: Logic for using index to lookup parameters needs to be in the Pod.
 - Drawback: CLIs and UIs are limited to using the "index" as the identity of a pod
   from a job.  They cannot easily say, for example `repeated failures on the pod processing banana.txt`.
 

docs/design/taint-toleration-dedicated.md

@@ -51,7 +51,7 @@ on a node but do not prevent it, taints that prevent a pod from starting on Kube
 if the pod's `NodeName` was written directly (i.e. pod did not go through the scheduler),
 and taints that evict already-running pods.
 [This comment](https://github.com/kubernetes/kubernetes/issues/3885#issuecomment-146002375)
-has more background on these diffrent scenarios. We will focus on the first
+has more background on these different scenarios. We will focus on the first
 kind of taint in this doc, since it is the kind required for the "dedicated nodes" use case.
 
 Implementing dedicated nodes using taints and tolerations is straightforward: in essence, a node that
@@ -264,7 +264,7 @@ their taint. Thus we need to ensure that a new node does not become "Ready" unti
 configured with its taints. One way to do this is to have an admission controller that adds the taint whenever
 a Node object is created.
 
-A quota policy may want to treat nodes diffrently based on what taints, if any,
+A quota policy may want to treat nodes differently based on what taints, if any,
 they have. For example, if a particular namespace is only allowed to access dedicated nodes,
 then it may be convenient to give the namespace unlimited quota. (To use finite quota,
 you'd have to size the namespace's quota to the sum of the sizes of the machines in the

docs/devel/README.md

@@ -79,7 +79,7 @@ Guide](../admin/README.md).
   Document style advice for contributors.
 
 * **Running a cluster locally** ([running-locally.md](running-locally.md)):
-  A fast and lightweight local cluster deployment for developement.
+  A fast and lightweight local cluster deployment for development.
 
 ## Developing against the Kubernetes API