Change a Workload Plane Node IP

Follow this procedure when you need to change a node workload plane IP within the defined workload plane CIDR, and you do not have a single IP for control plane and workload plane.

Note

If you want to change the current node workload plane IP and its CIDR, refer to the Change a Workload Plane CIDR procedure.

Important

It is not possible to change a workload plane node IP in the ARTESCA+ Veeam Unified Software Appliance.

Prerequisites

• A functioning ARTESCA installation

• Platform administrator rights

• SSH access to the server

Procedure

The new IP needs to be in the workload plane CIDR which is defined in the bootstrap configuration.

This procedure needs to be run on the workload plane node after the IP change.

1. Retrieve the current configured workload plane CIDR using Salt.

   [artesca-os@bootstrap ~]$
   

   sudo salt-call pillar.get networks:workload_plane:cidr
   

   local:
   - <workload-plane CIDR>
   

2. Discover the new IP using Salt.

   [artesca-os@bootstrap ~]$
   

   sudo salt-call state.sls metalk8s.node.grains
   

3. Check that the IP discovered is the right one.

   [artesca-os@bootstrap ~]$
   

   sudo salt-call grains.get metalk8s:workload_plane_ip
   

   local:
      <new workload-plane IP>
   

4. Reconfigure the node.

   [artesca-os@bootstrap ~]$
   

   sudo salt-call state.apply
   

5. Restart the local Ingress Controller pod.

   [artesca-os@bootstrap ~]$
   

   sudo crictl rmp -f $(sudo crictl pods -q \
      --label="io.kubernetes.pod.namespace=metalk8s-ingress" \
      --label="app.kubernetes.io/component=controller" \
      --label="app.kubernetes.io/instance=ingress-nginx" \
      --label="app.kubernetes.io/name=ingress-nginx")
   

6. From the bootstrap server, reconfigure the firewall using the installer of the current version.

   [artesca-os@bootstrap ~]$
   

   sudo ./artesca-installer configure-firewall