scottk/kubernetes
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/kubernetes.git synced 2025-11-03 19:58:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix misspellings of 'Kubernetes'

Browse Source
This commit is contained in:
Ivan Shvedunov
2016-10-13 22:49:21 +03:00
parent 9b3ca2fb0d
commit 2d420d2371
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cluster/gce/trusty/master.yaml
View File

@@ -205,7 +205,7 @@ Content-Disposition: attachment; filename="kube-master-health-monitoring.conf"
#upstart-job
description "Kubenetes master health monitoring"
description "Kubernetes master health monitoring"
start on stopped kube-docker

2
cluster/gce/trusty/node.yaml
View File

@@ -258,7 +258,7 @@ Content-Type: text/upstart-job; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="kube-node-health-monitoring.conf"
description "Kubenetes node health monitoring"
description "Kubernetes node health monitoring"
start on stopped kube-docker

2
cluster/vsphere/util.sh
View File

@@ -322,7 +322,7 @@ function setup-pod-routes {
done
# identify the subnet assigned to the node by the kubernertes controller manager.
# identify the subnet assigned to the node by the kubernetes controller manager.
KUBE_NODE_BRIDGE_NETWORK=()
for (( i=0; i<${#NODE_NAMES[@]}; i++)); do
printf " finding network of cbr0 bridge on node ${NODE_NAMES[$i]}\n"

2
docs/proposals/image-provenance.md
View File

@@ -61,7 +61,7 @@ Non-goals include:
* A third-party implementation of an image policy checker could optionally use ThirdPartyResource to store its policy.
* Kubernetes core code dealing with concepts of image layers, build processes, source repositories, etc.
* We expect there will be multiple PaaSes and/or de-facto programming environments, each with different takes on
these concepts. At any rate, Kuberenetes is not ready to be opinionated on these concepts.
these concepts. At any rate, Kubernetes is not ready to be opinionated on these concepts.
* Sending more information than strictly needed to a third-party service.
* Information sent by Kubernetes to a third-party service constitutes an API of Kubernetes, and we want to
avoid making these broader than necessary, as it restricts future evolution of Kubernetes, and makes

2
staging/src/k8s.io/client-go/copy.sh
View File

@@ -71,7 +71,7 @@ ls "${CLIENT_REPO}" | { grep -v '_tmp' || true; } | xargs rm -rf
mv "${CLIENT_REPO_TEMP}"/* "${CLIENT_REPO}"
rm -r "${CLIENT_REPO_TEMP}"
echo "moving vendor/k8s.io/kuberentes"
echo "moving vendor/k8s.io/kubernetes"
cp -rn "${CLIENT_REPO}"/vendor/k8s.io/kubernetes/. "${CLIENT_REPO}"/
rm -rf "${CLIENT_REPO}"/vendor/k8s.io/kubernetes
# client-go will share the vendor of the main repo for now. When client-go