Skip to content

Fix incorrect variable names for downstream clusters #848

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 23, 2025
Merged

Fix incorrect variable names for downstream clusters #848

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions asciidoc/product/atip-automated-provision.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1033,7 +1033,7 @@ spec:
name: multinode-cluster
----

The `Metal3Cluster` object specifies the control-plane endpoint that uses the `VIP` address already reserved (replacing the `$\{DOWNSTREAM_VIP_ADDRESS\}`) to be configured and the `noCloudProvider` because the three bare-metal nodes are used.
The `Metal3Cluster` object specifies the control-plane endpoint that uses the `VIP` address already reserved (replacing the `$\{EDGE_VIP_ADDRESS\}`) to be configured and the `noCloudProvider` because the three bare-metal nodes are used.
[,yaml]
----
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
Expand Down Expand Up @@ -1462,11 +1462,11 @@ stringData:

As you can see, the example shows the configuration to enable the interface with static IPs, as well as the configuration to enable the VLAN using the base interface, once the following variables are replaced with the actual values, according to your infrastructure:

- `$\{CONTROLPLANE1_INTERFACE\}` — The control-plane interface to be used for the edge cluster (for example, `eth0`). Including `identifier: mac-address` the naming is inspected automatically by the MAC address so any interface name can be used.
- `$\{CONTROLPLANE1_IP\}` — The IP address to be used as an endpoint for the edge cluster (must match with the kubeapi-server endpoint).
- `$\{CONTROLPLANE1_PREFIX\}` — The CIDR to be used for the edge cluster (for example, `24` if you want `/24` or `255.255.255.0`).
- `$\{CONTROLPLANE1_GATEWAY\}` — The gateway to be used for the edge cluster (for example, `192.168.100.1`).
- `$\{CONTROLPLANE1_MAC\}` — The MAC address to be used for the control-plane interface (for example, `00:0c:29:3e:3e:3e`).
- `$\{CONTROLPLANE_INTERFACE\}` — The control-plane interface to be used for the edge cluster (for example, `eth0`). Including `identifier: mac-address` the naming is inspected automatically by the MAC address so any interface name can be used.
- `$\{CONTROLPLANE_IP\}` — The IP address to be used as an endpoint for the edge cluster (must match with the kubeapi-server endpoint).
- `$\{CONTROLPLANE_PREFIX\}` — The CIDR to be used for the edge cluster (for example, `24` if you want `/24` or `255.255.255.0`).
- `$\{CONTROLPLANE_GATEWAY\}` — The gateway to be used for the edge cluster (for example, `192.168.100.1`).
- `$\{CONTROLPLANE_MAC\}` — The MAC address to be used for the control-plane interface (for example, `00:0c:29:3e:3e:3e`).
- `$\{DNS_SERVER\}` — The DNS to be used for the edge cluster (for example, `192.168.100.2`).
- `$\{VLAN_ID\}` — The VLAN ID to be used for the edge cluster (for example, `100`).

Expand Down