whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/kubernetes/kubernetes.github.io into release-1.8

Browse Source 
* 'master' of https://github.com/kubernetes/kubernetes.github.io: (33 commits)
  Added a prerequisite to using CoreDNS provider in federation (#5159)
  Edits "Creating a Deployment" section (#5195)
  Updating vSphere Cloud Provider Documentation (#5241)
  Update disruptions.md
  update OWNERS file
  Cilium network policy, update link: configure-pod-container -> administer-cluster
  Update volumes.md (#5214)
  Update images.md (#5212)
  fix resource quota redirect
  Fix link to Pod overview from concepts index
  fix the command output
  fix the command output
  Improve taint and toleration documentation
  Update deployment.md
  Update deployment.md
  Fix invalid internal links in federation doc
  Update images.md (#5034)
  Update docker-cli-to-kubectl.md (#5040)
  Update parallel-processing-expansion.md (#5060)
  Update cluster-management.md (#5130)
  ...
This commit is contained in:
Andrew Chen
2017-09-01 14:49:44 -07:00
parent 895a6074e2 d15b138d2e
commit 5edcbfd1f1
40 changed files with 502 additions and 391 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/cluster-management.md
+1 -1
View File
@@ -71,7 +71,7 @@ If your cluster runs short on resources you can easily add more machines to it i
If you're using GCE or GKE it's done by resizing Instance Group managing your Nodes. It can be accomplished by modifying number of instances on `Compute > Compute Engine > Instance groups > your group > Edit group` [Google Cloud Console page](https://console.developers.google.com) or using gcloud CLI:
```shell
gcloud compute instance-groups managed resize kubernetes-minion-group --size 42 --zone $ZONE
gcloud compute instance-groups managed resize kubernetes-minion-group --size=42 --zone=$ZONE
```
Instance Group will take care of putting appropriate image on new machines and start them, while Kubelet will register its Node with API server to make it available for scheduling. If you scale the instance group down, system will randomly choose Nodes to kill.
docs/tasks/administer-cluster/declare-network-policy.md
+1 -1
View File
@@ -12,7 +12,7 @@ This document helps you get started using the Kubernetes [NetworkPolicy API](/do
You'll need to have a Kubernetes cluster in place, with network policy support. There are a number of network providers that support NetworkPolicy, including:
* [Calico](/docs/tasks/configure-pod-container/calico-network-policy/)
* [Cilium](/docs/tasks/configure-pod-container/cilium-network-policy/)
* [Cilium](/docs/tasks/administer-cluster/cilium-network-policy/)
* [Romana](/docs/tasks/configure-pod-container/romana-network-policy/)
* [Weave Net](/docs/tasks/configure-pod-container/weave-network-policy/)
docs/tasks/administer-cluster/memory-constraint-namespace.md
+1 -1
View File
@@ -162,7 +162,7 @@ Error from server (Forbidden): error when creating "docs/tasks/administer-cluste
pods "constraints-mem-demo-3" is forbidden: minimum memory usage per Container is 500Mi, but request is 100Mi.
```
## Create a Pod that does not specify any CPU request or limit
## Create a Pod that does not specify any memory request or limit
docs/tasks/administer-cluster/securing-a-cluster.md
+1
View File
@@ -123,6 +123,7 @@ prevent cross talk, or advanced networking policy.
By default, there are no restrictions on which nodes may run a pod. Kubernetes offers a
[rich set of policies for controlling placement of pods onto nodes](/docs/concepts/configuration/assign-pod-node/)
and the [taint based pod placement and eviction](/docs/concepts/configuration/taint-and-toleration)
that are available to end users. For many clusters use of these policies to separate workloads
can be a convention that authors adopt or enforce via tooling.