knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

use consistent env variables from install section (#759) 

* use consistent env variables from install section

* fix existing lint problems causing test failures
This commit is contained in:
Ville Aikas 2019-01-14 13:54:31 -06:00 committed by Knative Prow Robot
parent 5de45fb22d
commit caed7ee6d0
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
serving/outbound-network-access.md
View File

@ -14,14 +14,18 @@ The scope varies depending on your platform:
- For Google Kubernetes Engine (GKE) run the following command to determine the
scope. Make sure to replace the variables or export these values first.
```shell
gcloud container clusters describe ${CLUSTER_ID} \
--zone=${GCP_ZONE} | grep -e clusterIpv4Cidr -e servicesIpv4Cidr
gcloud container clusters describe ${CLUSTER_NAME} \
--zone=${CLUSTER_ZONE} | grep -e clusterIpv4Cidr -e servicesIpv4Cidr
```
- For IBM Cloud Private run the following command:
```shell
cat cluster/config.yaml | grep service_cluster_ip_range
```
- For IBM Cloud Kubernetes Service use
`172.30.0.0/16,172.20.0.0/16,10.10.10.0/24`
- For Azure Container Service (ACS) use `10.244.0.0/16,10.240.0.0/16`
@ -32,8 +36,7 @@ The scope varies depending on your platform:
The `istio.sidecar.includeOutboundIPRanges` parameter in the `config-network`
map specifies the IP ranges that Istio sidecar intercepts. To allow outbound
access, replace the default parameter
value with the IP ranges of your cluster.
access, replace the default parameter value with the IP ranges of your cluster.
Run the following command to edit the `config-network` map: