Create Cluster Definition
To complete the Edge Installation process, an Edge host must become a member of a host cluster. You can add an Edge host to an existing host cluster of type Edge Native, or you can create a new host cluster for Edge hosts and make the Edge host a member.
Select the workflow that best fits your needs.
Create an Edge Native Host Cluster
Use the following steps to create a new host cluster so that you can add Edge hosts to the node pools.
Limitations
- In a multi-node cluster with PXK-E as its Kubernetes layer, you cannot change custom Network Interface Card (NIC). When you add an Edge host to such a cluster, leave the NIC field as its default value.
Prerequisites
- A registered Edge host.
Create Cluster
-
Log in to Palette.
-
Navigate to the left Main Menu and select Clusters.
-
Click on Add New Cluster.
-
Choose Edge Native for the cluster type and click Start Edge Native Configuration.
-
Give the cluster a name, description, and tags. Click on Next.
-
Select a cluster profile. If you don't have a cluster profile for Edge Native, refer to the Create Edge Native Cluster Profile guide. Click on Next after you have selected a cluster profile.
-
Review your cluster profile values and make changes as needed. Click on Next.
-
Provide the host cluster with the Virtual IP (VIP) address used by the physical site. Ensure that this VIP is not in a CIDR range that cannot routed through a proxy. In addition, ensure that this VIP does not overlap with any IP address already used by other hosts in your network, including your Edge hosts.
You can also select any SSH keys in case you need to remote into the host cluster. You can also provide a list of Network Time Protocol (NTP) servers. Click on Next.
-
The node configuration page is where you can specify what Edge hosts make up the host cluster. Assign Edge hosts to the control-plane-pool and the worker-pool. When you have completed configuring the node pools, click on Next.
-
(Optional) When you assign Edge hosts to node pools, you can optionally specify a static IP address for each Edge host. If you want to specify a static IP, toggle on Static IP and provide the following information:
| Field | Description |
|---|---|
| IP address | The static IP address assigned to your Edge host. This should be unique within your network. |
| Default gateway | The IP address of the default gateway for your cluster network. This gateway routes traffic from your cluster to external networks. |
| Subnet mask | The subnet mask of your cluster network. This defines the range of IP addresses within your cluster network. |
| DNS server | The IP address of the DNS server your cluster uses for domain resolution. |
If certain network information is already available, the corresponding fields will be pre-populated.
- (Optional) When you assign an Edge host to a node pool, if your Edge host has more than one NIC, you can optionally specify which Network Interface Controller (NIC) the Edge host will use to communicate with the cluster. When you select an Edge host, Palette displays a dropdown of all NICs present on the Edge host.
If the NIC is configured on the Edge host network, an IP address is displayed next to the name of the NIC. If the NIC is not configured on the Edge host network, you can specify its IP address, default gateway, subnet mask, as well as DNS server to configure it.
If you choose to change the default NIC used by your nodes in the control plane node pool, you need to make sure all the NICs in the control plane node pool share the same name. You also must make corresponding changes in the Kubernetes layer and the Container Network Interface (CNI) layer.
In the Kubernetes layer, enter a new parameter cluster.kubevipArgs.vip_interface and set its value to the name of the
NIC used by your control plane nodes. For example, if the NIC used by the nodes in your control plane pool is named
ens32, add the following two lines.
cluster:
kubevipArgs:
vip_interface: "ens32"
In the CNI layer, depending on which CNI pack you choose for your cluster profile, you need to make changes in the following locations.
- Calico
- Flannel
- Cilium
- Other
In the Calico pack YAML file default template, uncomment manifests.calico.env.calicoNode.IP_AUTODETECTION_METHOD and set its value to interface=INTERFACE_NAME. Replace INTERFACE_NAME with the name of the NIC in your control plane node pool. For example, set IP_AUTODETECTION_METHOD to "interface=eno32" if the NIC name of the nodes in your control plane pool is eno32.
manifests:
calico:
...
env:
# Additional env variables for calico-node
calicoNode:
#IPV6: "autodetect"
#FELIX_IPV6SUPPORT: "true"
#CALICO_IPV6POOL_NAT_OUTGOING: "true"
#CALICO_IPV4POOL_CIDR: "192.168.0.0/16"
IP_AUTODETECTION_METHOD: "interface=eno32"
In the Flannel pack YAML file, add a line - "--iface=INTERFACE_NAME" in the default template under
charts.flannel.args. Replace INTERFACE_NAME with the name of the NIC. For example, add the line - "--iface=eno32
if the NIC name of your control plane nodes is eno32.
charts:
flannel:
...
# flannel command arguments
args:
- "--ip-masq"
- "--kube-subnet-mgr"
- "--iface=eno32"
You do not need to make any adjustments to the Cilium pack.
If you are using other CNIs, refer to the documentation of your selected CNI and configure it to make sure that it picks the right NIC on your Edge hosts.
After you create the cluster, you will not be able to change the IP address or NIC of your existing Edge hosts unless you remove and re-add them back to the cluster.
-
The Settings page is where you can configure a patching schedule, security scans, backup settings, and set up Role-Based Access Control (RBAC). Review the settings and make changes if needed. Click on Validate.
-
Review the settings summary and click on Finish Configuration to deploy the cluster.
After you create the cluster, the Palette Edge Host agent will start the installation process. You can track the installation progress in Palette. The cluster overview page displays a summary of the progress. Use the Events tab to review detailed logs.
Validate
-
Log in to Palette.
-
Navigate to the left Main Menu and select Clusters.
-
Select the host cluster you created to view its details page.
-
Review the Cluster Status. Ensure the Cluster Status field displays Running.
You can also use the command kubectl get nodes to review the status of all nodes in the cluster. Check out the
Access Cluster with CLI guide to learn how to use kubectl with a host
cluster.
Add an Edge Host to a Host Cluster
You can add Edge hosts to the node pool of an existing host cluster. Use the following steps to add the Edge host to the node pool.
Limitations
- In a multi-node cluster with PXK-E as its Kubernetes layer, you cannot change custom Network Interface Card (NIC). When you add an Edge host to such a cluster, leave the NIC field as its default value.
Prerequisites
-
A registered Edge host.
-
A host cluster of type Edge Native.
When adding a new Edge host to an existing cluster, ensure you are not creating a scenario where etcd could fail in establishing a quorum. Quorum failures typically result when there is an even number of nodes. To learn more, check out the resource from the etcd documentation titled Why an odd number of cluster members.
Add Edge Host to Node Pool
-
Log in to Palette.
-
Navigate to the left Main Menu and select Clusters.
-
Use the Cloud Types drop-down Menu and select Edge Native.
-
Select the host cluster to add the registered Edge host.
-
Click on the Nodes tab.
-
Select the node pool to add the Edge host and click the Edit button.
-
Navigate to the Edge Hosts drop-down Menu and select your Edge host.
-
(Optional) When you select your Edge host, you can optionally specify a static IP address for the Edge host. If you want to specify a static IP, toggle on Static IP and provide the following information:
| Field | Description |
|---|---|
| IP Address | The static IP address assigned to your Edge host. This should be unique within your network. |
| Default gateway | The IP address of the default gateway for your cluster network. This gateway routes traffic from your cluster to external networks. |
| Subnet mask | The subnet mask of your cluster network. This defines the range of IP addresses within your cluster network. |
| DNS server | The IP address of the DNS server your cluster uses for domain resolution. |
If certain network information is already available, the corresponding fields will be pre-populated.
- (Optional) When you assign an Edge host to a node pool, if your Edge host has more than one NIC, you can optionally specify which Network Interface Controller (NIC) the Edge host will use to communicate with the cluster. When you select an Edge host, Palette displays a dropdown of all NICs present on the Edge host.
If the NIC is configured on the Edge host network, an IP address is displayed next to the name of the NIC. If the NIC is not configured on the Edge host network, you can specify its IP address, default gateway, subnet mask, as well as DNS server to configure it.
If you choose to change the default NIC used by your nodes, you need to make sure all the NICs in the control plane node pool share the same name. You also must make corresponding changes in the Kubernetes layer and the CNI layer.
In the Kubernetes layer, enter a new parameter cluster.kubevipArgs.vip_interface and set its value to the name of the
NIC used by your control plane nodes. For example, if the NIC used by the nodes in your control plane pool is named
ens32, add the following two lines.
cluster:
kubevipArgs:
vip_interface: "ens32"
In the CNI layer, depending on which CNI pack you choose for your cluster profile, you need to make changes in the following locations.
- Calico
- Flannel
- Cilium
- Other
In the Calico pack YAML file default template, uncomment manifests.calico.env.calicoNode.IP_AUTODETECTION_METHOD and set its value to interface=INTERFACE_NAME. Replace INTERFACE_NAME with the name of the NIC in your control plane node pool. For example, set IP_AUTODETECTION_METHOD to "interface=eno32" if the NIC name of the nodes in your control plane pool is eno32.
manifests:
calico:
...
env:
# Additional env variables for calico-node
calicoNode:
#IPV6: "autodetect"
#FELIX_IPV6SUPPORT: "true"
#CALICO_IPV6POOL_NAT_OUTGOING: "true"
#CALICO_IPV4POOL_CIDR: "192.168.0.0/16"
IP_AUTODETECTION_METHOD: "interface=eno32"
In the Flannel pack YAML file, add a line - "--iface=INTERFACE_NAME" in the default template under
charts.flannel.args. Replace INTERFACE_NAME with the name of the NIC. For example, add the line - "--iface=eno32
if the NIC name of your control plane nodes is eno32.
charts:
flannel:
...
# flannel command arguments
args:
- "--ip-masq"
- "--kube-subnet-mgr"
- "--iface=eno32"
You do not need to make any adjustments to the Cilium pack.
If you are using other CNIs, refer to the documentation of your selected CNI and configure it to make sure that it picks the right NIC on your Edge hosts.
After you add the Edge host to your cluster, you will not be able to change its IP address unless you remove and re-add them back to the cluster.
- Confirm your changes.
The Palette Edge Host agent will start the installation process. You can track the installation progress in Palette. The cluster overview page displays a summary of the progress. Use the Events tab to review detailed logs.
Validate
-
Log in to Palette.
-
Navigate to the left Main Menu and select Clusters.
-
Select the host cluster you created to view its details page.
-
Review the Cluster Status. Ensure the Cluster Status field displays Running.
You can also use the command kubectl get nodes to review the status of all nodes in the cluster. Check out the
Access Cluster with CLI to learn how to use kubectl with a host
cluster.