VMware Aria Automation 8.16

8.18 8.17 8.16 8.14 8.13 all
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands Русский 繁體中文 English

Configure
Automation Orchestrator
 Kubernetes CIDR

You can change the Kubernetes Classless Inter-domain Routing (CIDR) subnet masks after deployment.
  • 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.
    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 the
    service-cidr
     property. Each subnet value must be added separately.
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
.
For information on changing the CIDR configuration during appliance deployment, see Download and Deploy the Automation Orchestrator Appliance.
  1. Log in to the
    Automation Orchestrator Appliance
     as
    root
    .
  2. Run the
    vracli upgrade exec -y --prepare --profile k8s-subnets
     command.
  3. Back up your
    Automation Orchestrator
     deployment by taking a virtual machine (VM) snapshot. See Take a Snapshot of a Virtual Machine.
    Automation Orchestrator
     8.x does not currently support memory snapshots. Before taking the snapshot of your
    Automation Orchestrator
     deployment, verify that the
    Snapshot the virtual machine’s memory
     option is deactivated.
  4. Change the values of the cluster CIDR and service CIDR subnets by running the
    vracli network k8s-subnets
     command.
    vracli network k8s-subnets --cluster-cidr <CIDR_value> --service-cidr <CIDR_value>
  5. To finish the CIDR configuration process, run the
    vracli upgrade exec
     command.

Content feedback and comments