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

Update scratch.md (#7516)

Browse Source
This commit is contained in:
Weibin Lin
2018-02-26 23:49:43 +08:00
committed by k8s-ci-robot
parent 0955d6be90
commit e0ca08771e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/scratch.md
+2 -2
View File
@@ -91,7 +91,7 @@ to implement one of the above options:
- You can also write your own. - You can also write your own.
- **Compile support directly into Kubernetes** - **Compile support directly into Kubernetes**
- This can be done by implementing the "Routes" interface of a Cloud Provider module. - This can be done by implementing the "Routes" interface of a Cloud Provider module.
- The Google Compute Engine ([GCE](/docs/getting-started-guides/gce/)/) and [AWS](/docs/getting-started-guides/aws/) guides use this approach. - The Google Compute Engine ([GCE](/docs/getting-started-guides/gce/)) and [AWS](/docs/getting-started-guides/aws/) guides use this approach.
- **Configure the network external to Kubernetes** - **Configure the network external to Kubernetes**
- This can be done by manually running commands, or through a set of externally maintained scripts. - This can be done by manually running commands, or through a set of externally maintained scripts.
- You have to implement this yourself, but it can give you an extra degree of flexibility. - You have to implement this yourself, but it can give you an extra degree of flexibility.
@@ -116,7 +116,7 @@ You will need to select an address range for the Pod IPs. Note that IPv6 is not
Kubernetes also allocates an IP to each [service](/docs/concepts/services-networking/service/). However, Kubernetes also allocates an IP to each [service](/docs/concepts/services-networking/service/). However,
service IPs do not necessarily need to be routable. The kube-proxy takes care service IPs do not necessarily need to be routable. The kube-proxy takes care
of translating Service IPs to Pod IPs before traffic leaves the node. You do of translating Service IPs to Pod IPs before traffic leaves the node. You do
need to Allocate a block of IPs for services. Call this need to allocate a block of IPs for services. Call this
`SERVICE_CLUSTER_IP_RANGE`. For example, you could set `SERVICE_CLUSTER_IP_RANGE`. For example, you could set
`SERVICE_CLUSTER_IP_RANGE="10.0.0.0/16"`, allowing 65534 distinct services to `SERVICE_CLUSTER_IP_RANGE="10.0.0.0/16"`, allowing 65534 distinct services to
be active at once. Note that you can grow the end of this range, but you be active at once. Note that you can grow the end of this range, but you