Clarify use of --pod-cidr and --service-cluster-ip-range (#9751)

* Clarify use of --pod-cidr and --service-cluster-ip-range

Clarified where flags are used. Customer reported confusion in case# 101388 because commands were not specified.

* hyperlink fix

fixed issues with hyperlinks

* Made the UCP CLI Links Generic

* Uppercase UCP
This commit is contained in:
Nathan Jones 2019-11-13 10:56:47 -05:00 committed by Olly P
parent 98e6aca2d3
commit 3802ec8822
1 changed files with 6 additions and 3 deletions

View File

@ -111,12 +111,14 @@ conflict with the underlying infrastructure:
* The Pod Network - Each Pod in Kubernetes is given an IP address from either
the Calico or Azure IPAM services. In a default installation Pods are given
IP addresses on the `192.168.0.0/16` range. This can be customized at install
time using the `--pod-cidr` flag.
time by passing the `--pod-cidr` flag to the
[UCP install command](/reference/ucp/{{ site.ucp_version }}/cli/install/).
* The Services Network - When a user exposes a Service in Kubernetes it is
accessible via a VIP, this VIP comes from a Cluster IP Range. By default on UCP
this range is `10.96.0.0/16`. From UCP 3.1.8 and onwards this value can be
changed at install time with the `--service-cluster-ip-range` flag.
changed at install time by passing the `--service-cluster-ip-range` flag to
the [UCP install command](/reference/ucp/{{ site.ucp_version }}/cli/install/).
## Avoid firewall conflicts
@ -160,7 +162,8 @@ address or port number.
If you want to install UCP in a high-availability configuration that uses
a load balancer in front of your UCP controllers, include the appropriate IP
address and FQDN of the load balancer's VIP by using
one or more `--san` flags in the [install command](/reference/ucp/3.0/cli/install.md)
one or more `--san` flags in the
[UCP install command](/reference/ucp/{{ site.ucp_version }}/cli/install/)
or when you're asked for additional SANs in interactive mode.
[Learn about high availability](../configure/set-up-high-availability.md).