Creating a workload CAPX cluster in a Nutanix Flow VPC¶
The scenario and features described on this page are experimental. It's important to note that they have not been fully validated.
Nutanix Flow VPCs are only validated with CAPX 1.1.3+
Nutanix Flow Virtual Networking allows users to create Virtual Private Clouds (VPCs) with Overlay networking. The steps below will illustrate how a CAPX cluster can be deployed inside an overlay subnet (NAT) inside a VPC while the management cluster resides outside of the VPC.
- Request a floating IP
- Link the floating IP to an internal IP address inside the overlay subnet that will be used to deploy the CAPX cluster. This address will be assigned to the CAPX loadbalancer. To prevent IP conflicts, make sure the IP address is not part of the IP-pool defined in the subnet.
- Generate a
cluster.yamlfile with the required CAPX cluster configuration where the
CONTROL_PLANE_ENDPOINT_IPis set to the floating IP requested in the first step. Refer to the Getting Started page for more information on how to generate a
cluster.yamlfile. Do not apply the
- Edit the
cluster.yamlfile and search for the
- Modify the
spec.kubeadmConfigSpec.files.*.contentattribute and change the
kube-vipdefinition similar to the example below.
- Apply the
- When the CAPX workload cluster is deployed, it will be reachable via the floating IP.
kind: KubeadmControlPlane spec: kubeadmConfigSpec: files: - content: | apiVersion: v1 kind: Pod metadata: name: kube-vip namespace: kube-system spec: containers: - env: - name: address value: "<internal overlay subnet address>"