github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

typofix - https://github.com/vlajos/misspell_fixer

Browse Source
This commit is contained in:
Veres Lajos
2015-08-08 22:29:57 +01:00
parent 2bfa9a1f98
commit 9f77e49109
116 changed files with 160 additions and 160 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/admin/cluster-large.md
View File

@@ -88,7 +88,7 @@ To avoid running into cluster addon resource issues, when creating a cluster wit
* [Kibana](http://releases.k8s.io/HEAD/cluster/addons/fluentd-elasticsearch/kibana-controller.yaml)
* Scale number of replicas for the following addons, if used, along with the size of cluster (there are multiple replicas of each so increasing replicas should help handle increased load, but, since load per replica also increases slightly, also consider increasing CPU/memory limits):
* [elasticsearch](http://releases.k8s.io/HEAD/cluster/addons/fluentd-elasticsearch/es-controller.yaml)
* Increase memory and CPU limits sligthly for each of the following addons, if used, along with the size of cluster (there is one replica per node but CPU/memory usage increases slightly along with cluster load/size as well):
* Increase memory and CPU limits slightly for each of the following addons, if used, along with the size of cluster (there is one replica per node but CPU/memory usage increases slightly along with cluster load/size as well):
* [FluentD with ElasticSearch Plugin](http://releases.k8s.io/HEAD/cluster/saltbase/salt/fluentd-es/fluentd-es.yaml)
* [FluentD with GCP Plugin](http://releases.k8s.io/HEAD/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml)

4
docs/admin/cluster-management.md
View File

@@ -35,7 +35,7 @@ Documentation for other releases can be found at
This document describes several topics related to the lifecycle of a cluster: creating a new cluster,
upgrading your cluster's
master and worker nodes, performing node maintainence (e.g. kernel upgrades), and upgrading the Kubernetes API version of a
master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a
running cluster.
## Creating and configuring a Cluster
@@ -132,7 +132,7 @@ For pods with a replication controller, the pod will eventually be replaced by a
For pods with no replication controller, you need to bring up a new copy of the pod, and assuming it is not part of a service, redirect clients to it.
Perform maintainence work on the node.
Perform maintenance work on the node.
Make the node schedulable again:

2
docs/admin/etcd.md
View File

@@ -41,7 +41,7 @@ objects.
Access Control: give *only* kube-apiserver read/write access to etcd. You do not
want apiserver's etcd exposed to every node in your cluster (or worse, to the
internet at large), because access to etcd is equivilent to root in your
internet at large), because access to etcd is equivalent to root in your
cluster.
Data Reliability: for reasonable safety, either etcd needs to be run as a

4
docs/api-reference/definitions.html
View File

@@ -4224,7 +4224,7 @@ span.icon > [class^="icon-"], span.icon > [class*=" icon-"] { cursor: default; }
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">hostPath</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">a HostPath provisioned by a developer or tester; for develment use only; see <a href="http://releases.k8s.io/HEAD/docs/user-guide/volumes.md#hostpath">http://releases.k8s.io/HEAD/docs/user-guide/volumes.md#hostpath</a></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">a HostPath provisioned by a developer or tester; for development use only; see <a href="http://releases.k8s.io/HEAD/docs/user-guide/volumes.md#hostpath">http://releases.k8s.io/HEAD/docs/user-guide/volumes.md#hostpath</a></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"><a href="#_v1_hostpathvolumesource">v1.HostPathVolumeSource</a></p></td>
<td class="tableblock halign-left valign-top"></td>
@@ -5099,7 +5099,7 @@ span.icon > [class^="icon-"], span.icon > [class*=" icon-"] { cursor: default; }
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">lastTimestamp</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">the time at which the most recent occurance of this event was recorded</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">the time at which the most recent occurrence of this event was recorded</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>

2
docs/devel/development.md
View File

@@ -87,7 +87,7 @@ Note: If you have write access to the main repository at github.com/GoogleCloudP
git remote set-url --push upstream no_push
```
### Commiting changes to your fork
### Committing changes to your fork
```sh
git commit

2
docs/devel/making-release-notes.md
View File

@@ -40,7 +40,7 @@ This documents the process for making release notes for a release.
Find the most-recent PR that was merged with the previous .0 release. Remember this as $LASTPR.
_TODO_: Figure out a way to record this somewhere to save the next release engineer time.
Find the most-recent PR that was merged with the current .0 release. Remeber this as $CURRENTPR.
Find the most-recent PR that was merged with the current .0 release. Remember this as $CURRENTPR.
### 2) Run the release-notes tool

2
docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
View File

@@ -1,4 +1,4 @@
## This file is used as input to deployment script, which ammends it as needed.
## This file is used as input to deployment script, which amends it as needed.
## More specifically, we need to add peer hosts for each but the elected peer.
coreos:

2
docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
View File

@@ -1,4 +1,4 @@
## This file is used as input to deployment script, which ammends it as needed.
## This file is used as input to deployment script, which amends it as needed.
## More specifically, we need to add environment files for as many nodes as we
## are going to deploy.

4
docs/getting-started-guides/docker-multinode.md
View File

@@ -87,7 +87,7 @@ cd kubernetes/cluster/docker-multinode
`Master done!`
See [here](docker-multinode/master.md) for detailed instructions explaination.
See [here](docker-multinode/master.md) for detailed instructions explanation.
## Adding a worker node
@@ -104,7 +104,7 @@ cd kubernetes/cluster/docker-multinode
`Worker done!`
See [here](docker-multinode/worker.md) for detailed instructions explaination.
See [here](docker-multinode/worker.md) for detailed instructions explanation.
## Testing your cluster

6
docs/man/man1/kubectl-namespace.1
View File

@@ -3,7 +3,7 @@
.SH NAME
.PP
kubectl namespace \- SUPERCEDED: Set and view the current Kubernetes namespace
kubectl namespace \- SUPERSEDED: Set and view the current Kubernetes namespace
.SH SYNOPSIS
@@ -13,10 +13,10 @@ kubectl namespace \- SUPERCEDED: Set and view the current Kubernetes namespace
.SH DESCRIPTION
.PP
SUPERCEDED: Set and view the current Kubernetes namespace scope for command line requests.
SUPERSEDED: Set and view the current Kubernetes namespace scope for command line requests.
.PP
namespace has been superceded by the context.namespace field of .kubeconfig files. See 'kubectl config set\-context \-\-help' for more details.
namespace has been superseded by the context.namespace field of .kubeconfig files. See 'kubectl config set\-context \-\-help' for more details.
.SH OPTIONS

2
docs/user-guide/kubectl/kubectl.md
View File

@@ -91,7 +91,7 @@ kubectl
* [kubectl get](kubectl_get.md) - Display one or many resources
* [kubectl label](kubectl_label.md) - Update the labels on a resource
* [kubectl logs](kubectl_logs.md) - Print the logs for a container in a pod.
* [kubectl namespace](kubectl_namespace.md) - SUPERCEDED: Set and view the current Kubernetes namespace
* [kubectl namespace](kubectl_namespace.md) - SUPERSEDED: Set and view the current Kubernetes namespace
* [kubectl patch](kubectl_patch.md) - Update field(s) of a resource by stdin.
* [kubectl port-forward](kubectl_port-forward.md) - Forward one or more local ports to a pod.
* [kubectl proxy](kubectl_proxy.md) - Run a proxy to the Kubernetes API server

6
docs/user-guide/kubectl/kubectl_namespace.md
View File

@@ -33,14 +33,14 @@ Documentation for other releases can be found at
## kubectl namespace
SUPERCEDED: Set and view the current Kubernetes namespace
SUPERSEDED: Set and view the current Kubernetes namespace
### Synopsis
SUPERCEDED: Set and view the current Kubernetes namespace scope for command line requests.
SUPERSEDED: Set and view the current Kubernetes namespace scope for command line requests.
namespace has been superceded by the context.namespace field of .kubeconfig files. See 'kubectl config set-context --help' for more details.
namespace has been superseded by the context.namespace field of .kubeconfig files. See 'kubectl config set-context --help' for more details.
```

2
docs/user-guide/secrets.md
View File

@@ -160,7 +160,7 @@ See another example of creating a secret and a pod that consumes that secret in
### Manually specifying an imagePullSecret
Use of imagePullSecrets is desribed in the [images documentation](images.md#specifying-imagepullsecrets-on-a-pod)
Use of imagePullSecrets is described in the [images documentation](images.md#specifying-imagepullsecrets-on-a-pod)
### Automatic use of Manually Created Secrets