The OpenStackClusterSpec allows you to define how the cluster connects to OpenStack networks. You can choose between having the provider manage the network or using existing OpenStack resources.
Managed Networking
If you provide managedSubnets ([]SubnetSpec), the cluster actuator will automatically create a network, subnets with the defined CIDR, and a router.
- Note: Currently, only one IPv4 subnet is supported via this method.
- MTU: You can set
networkMTU (int) to address fragmentation. This requires the net-mtu neutron API extension. If left empty, the default OpenStack network service MTU is used.
Existing Networking
If you do not use managedSubnets, you can point to existing resources:
network: Specify an existing NetworkParam to use.subnets: Specify existing []SubnetParam. All subnets must reside in the specified network. If no subnets are specified, all subnets in the network will be used.primarySubnet: If multiple subnets are provided, use this to identify the primary subnet for load balancer VIP allocation and node member registration. If not specified, the first subnet in the resolved list is used.router: Specify an existing RouterParam to avoid creating a new router.
External Connectivity
externalNetwork: The OpenStack Network used for public internet access. If not defined, the controller attempts to use a single existing external network. If multiple exist and none are specified, it results in an error unless disableExternalNetwork is true.disableExternalNetwork: Set to true to prevent the cluster from attempting to connect to an external network (useful for provider networks).externalRouterIPs: An array of []ExternalRouterIPParam used if the router requires a fixed IP in a specific subnet.
# Example conceptual configuration for existing networking
spec:
network:
name: existing-network-name
subnets:
- id: "subnet-uuid-1"
- id: "subnet-uuid-2"
primarySubnet: "subnet-uuid-1"
router:
id: "router-uuid"
