Create subnets for a managed cluster using web UI¶
After creating the MetalLB configuration as described in Configure MetalLB
and before creating an L2 template, create the required subnets to use in the
L2 template to allocate IP addresses for the managed cluster nodes.
To create subnets for a managed cluster using web UI:
Log in to the Container Cloud web UI with the operator permissions.
Switch to the required non-default project using the
Switch Project action icon located on top of the main left-side
navigation panel.
Available in the web UI since 2.28.0 (17.3.0 and 16.3.0).
Storage access subnet.
Storage replication
Available in the web UI since 2.28.0 (17.3.0 and 16.3.0).
Storage replication subnet.
Custom
Custom subnet. For example, external or Kubernetes workloads.
MetalLB
Services subnet(s).
Warning
Since Container Cloud 2.28.0 (Cluster releases 17.3.0
and 16.3.0), disregard this parameter during subnet creation.
Configure MetalLB separately as described in
Configure MetalLB.
This parameter will be removed from the Container Cloud web UI
in one of the following releases.
Cluster name that the subnet is being created for. Not required only
for the DHCP subnet.
CIDR
A valid IPv4 address of the subnet in the CIDR notation, for example,
10.11.0.0/24.
Include RangesOptional
A comma-separated list of IP address ranges within the given CIDR that should
be used in the allocation of IPs for nodes. The gateway, network, broadcast,
and DNSaddresses will be excluded (protected) automatically if they intersect
with one of the range. The IPs outside the given ranges will not be used in
the allocation. Each element of the list can be either an interval
10.11.0.5-10.11.0.70 or a single address 10.11.0.77.
The includeRanges parameter is mutually exclusive with excludeRanges.
Exclude RangesOptional
A comma-separated list of IP address ranges within the given CIDR that should
not be used in the allocation of IPs for nodes. The IPs within the given CIDR
but outside the given ranges will be used in the allocation.
The gateway, network, broadcast, and DNS addresses will be excluded
(protected) automatically if they are included in the CIDR.
Each element of the list can be either an interval 10.11.0.5-10.11.0.70
or a single address 10.11.0.77. The excludeRanges parameter
is mutually exclusive with includeRanges.
GatewayOptional
A valid IPv4 gateway address, for example, 10.11.0.9. Does not apply
to the MetalLB subnet.
Nameservers
IP addresses of nameservers separated by a comma. Does not apply
to the DHCP and MetalLB subnet types.
Use whole CIDR
Optional. Select to use the whole IPv4 address range that is set in
the CIDR field. Useful when defining single IP address (/32),
for example, in the Cluster API load balancer (LB) subnet.
If not set, the network address and broadcast address in the IP
subnet are excluded from the address allocation.
Labels
Key-value pairs attached to the selected subnet:
MetalLB:
Warning
Since Container Cloud 2.28.0 (Cluster releases 17.3.0
and 16.3.0), disregard this label during subnet creation.
Configure MetalLB separately as described in
Configure MetalLB.
The label will be removed from the Container Cloud web UI in one
of the following releases.
metallb/address-pool-name
Name of the subnet address pool. Exemplary values:
services, default, external, services-pxe.
The latter label is dedicated for management clusters only.
For details about address pool names of a management cluster,
see Separate PXE and management networks.
metallb/address-pool-auto-assign
Enables automatic assignment of address pool. Boolean.
metallb/address-pool-protocol
Defines the address pool protocol. Possible values:
layer2 - announcement using the ARP protocol.
bgp - announcement using the BGP protocol. Technology
Preview.
Click Add a label and assign the first custom label
with the required name and value. To assign consecutive labels,
use the + button located in the right side of the
Labels section.
Click Create.
In the Networks tab, verify the status of the created
subnet:
Ready - object is operational.
Error - object is non-operational. Hover over the status
to obtain details of the issue.
Note
To verify subnet details, in the Networks tab,
click the More action icon in the last column of the
required subnet and select Subnet info.
Before 2.26.0 (17.1.0, 16.1.0)
In the Clusters tab, click the required cluster and scroll
down to the Subnets section.
Click Add Subnet.
Fill out the Add new subnet form as required:
Subnet Name
Subnet name.
CIDR
A valid IPv4 CIDR, for example, 10.11.0.0/24.
Include RangesOptional
A comma-separated list of IP address ranges within the given CIDR that should
be used in the allocation of IPs for nodes. The gateway, network, broadcast,
and DNSaddresses will be excluded (protected) automatically if they intersect
with one of the range. The IPs outside the given ranges will not be used in
the allocation. Each element of the list can be either an interval
10.11.0.5-10.11.0.70 or a single address 10.11.0.77.
The includeRanges parameter is mutually exclusive with excludeRanges.
Exclude RangesOptional
A comma-separated list of IP address ranges within the given CIDR that should
not be used in the allocation of IPs for nodes. The IPs within the given CIDR
but outside the given ranges will be used in the allocation.
The gateway, network, broadcast, and DNS addresses will be excluded
(protected) automatically if they are included in the CIDR.
Each element of the list can be either an interval 10.11.0.5-10.11.0.70
or a single address 10.11.0.77. The excludeRanges parameter
is mutually exclusive with includeRanges.