You can change the Kubernetes Classless Inter-domain Routing (CIDR) subnet masks after deployment.
The Automation Orchestrator Appliance configures and runs a Kubernetes cluster. The pods and services in this cluster are deployed in separate IPv4 subnets, represented by the internal cluster CIDR and internal service CIDR, respectively. The default values of the subnet masks set during OVF deployment are the following:
Kubernetes network property | Default value | Property description |
cluster-cidr |
10.244.0.0/22 | The CIDR used for pods running inside the Kubernetes cluster. |
service-cidr |
10.244.4.0/22 | The CIDR used for Kubernetes services inside the Kubernetes cluster. |
The default CIDR network addresses can create a conflict with outside private networks that you might be using. In such scenarios, you can change the configuration of these CIDR values either during or after deploying your Automation Orchestrator Appliance.
Note: For information on changing the CIDR configuration during appliance deployment, see
Download and Deploy the Automation Orchestrator Appliance.
Prerequisites
- Verify that the CIDR address values support at least 1024 hosts.
- The internal cluster CIDR and internal service CIDR must not share the same subnet value.
- The CIDR value for one of the subnets cannot include the value you want to add to the other subnet.
Note: For example, the
cluster-cidr
value cannot be 10.244.4.0/22 10.244.4.0/24, because this would also include the subnet value for theservice-cidr
property. Each subnet value must be added separately.