Create an L2 template for a MOSK storage node

Caution

Modification of L2 templates in use is only allowed with a mandatory validation step from the infrastructure operator to prevent accidental cluster failures due to unsafe changes. The list of risks posed by modifying L2 templates includes:

• Services running on hosts cannot reconfigure automatically to switch to the new IP addresses and/or interfaces.

• Connections between services are interrupted unexpectedly, which can cause data loss.

• Incorrect configurations on hosts can lead to irrevocable loss of connectivity between services and unexpected cluster partition or disassembly.

For details, see Modify network configuration on an existing machine.

According to the reference architecture, MOSK storage nodes in the MOSK cluster must be connected to the following networks:

• PXE network

• LCM network

• Kubernetes workloads network

• Storage access network

• Storage replication network

To create L2 templates for MOSK storage nodes:

1. Add L2 templates to the mosk-l2templates.yml file using the following example. Adjust the values of parameters according to the specification of your environment.

   Example of an L2 template for a MOSK storage node

   apiVersion: ipam.mirantis.com/v1alpha1
   kind: L2Template
   metadata:
     labels:
       kaas.mirantis.com/provider: baremetal
       kaas.mirantis.com/region: region-one
       cluster.sigs.k8s.io/cluster-name: mosk-cluster-name
       rack1-mosk-storage: "true"
     name: rack1-mosk-storage
     namespace: mosk-namespace-name
   spec:
     autoIfMappingPrio:
     - provision
     - eno
     - ens
     - enp
     l3Layout:
     - subnetName: rack1-k8s-lcm
       scope: namespace
     - subnetName: rack1-k8s-pods
       scope: namespace
     - subnetName: rack1-ceph-public
       scope: namespace
     - subnetName: rack1-ceph-cluster
       scope: namespace
     npTemplate: |-
       version: 2
       ethernets:
         {{nic 0}}:
           dhcp4: false
           dhcp6: false
           match:
             macaddress: {{mac 0}}
           set-name: {{nic 0}}
           mtu: 9000
         {{nic 1}}:
           dhcp4: false
           dhcp6: false
           match:
             macaddress: {{mac 1}}
           set-name: {{nic 1}}
           mtu: 9000
         {{nic 2}}
           dhcp4: false
           dhcp6: false
           match:
             macaddress: {{mac 2}}
           set-name: {{nic 2}}
           mtu: 9000
         {{nic 3}}:
           dhcp4: false
           dhcp6: false
           match:
             macaddress: {{mac 3}}
           set-name: {{nic 3}}
           mtu: 9000
       bonds:
         bond0:
           mtu: 9000
           parameters:
             mode: 802.3ad
             mii-monitor-interval: 100
           interfaces:
           - {{nic 0}}
           - {{nic 1}}
         bond1:
           mtu: 9000
           parameters:
             mode: 802.3ad
             mii-monitor-interval: 100
           interfaces:
           - {{nic 2}}
           - {{nic 3}}
       vlans:
         k8s-lcm-v:
           id: 403
           link: bond0
           mtu: 9000
         k8s-pods-v:
           id: 408
           link: bond0
           mtu: 9000
         stor-frontend:
           id: 404
           link: bond0
           addresses:
           - {{ip "stor-frontend:rack1-ceph-public"}}
           mtu: 9000
           routes:
           - to: 10.199.16.0/22 # aggregated address space for Ceph public network
             via: {{ gateway_from_subnet "rack1-ceph-public" }}
         stor-backend:
           id: 405
           link: bond1
           addresses:
           - {{ip "stor-backend:rack1-ceph-cluster"}}
           mtu: 9000
           routes:
           - to: 10.199.32.0/22 # aggregated address space for Ceph cluster network
             via: {{ gateway_from_subnet "rack1-ceph-cluster" }}
       bridges:
         k8s-lcm:
           interfaces: [k8s-lcm-v]
           addresses:
           - {{ ip "k8s-lcm:rack1-k8s-lcm" }}
           nameservers:
             addresses: {{nameservers_from_subnet "rack1-k8s-lcm"}}
           gateway4: {{ gateway_from_subnet "rack1-k8s-lcm" }}
         k8s-pods:
           interfaces: [k8s-pods-v]
           addresses:
           - {{ip "k8s-pods:k8s-pods-subnet"}}
           mtu: 9000
           routes:
             - to: 10.199.0.0/22 # aggregated address space for Kubernetes workloads
               via: {{gateway_from_subnet "rack1-k8s-pods"}}
   

   Note

   The kaas.mirantis.com/region label is removed from all MOSK objects in 24.1. Therefore, do not add the label starting with this release. On existing clusters updated to this release, or if added manually, MOSK ignores this label.

   Note

   Before MOSK 23.3, an L2 template requires clusterRef: <clusterName> in the spec section. Since MOSK 23.3, this parameter is deprecated and automatically migrated to the cluster.sigs.k8s.io/cluster-name: <clusterName> label.

2. Proceed with the L2 template configuration procedure described in Create an L2 template for a new cluster.