Cloud being used: bare-metal
Installation method: yum over hybrid VM/bare-metal
Host OS: Centos 7.6
I have a networking question for our kubernetes deployments. We have an existing SLURM HPC cluster with physical nodes and VM master controllers. We also have a two-node Kubernetes cluster (both VMs). We would like to share the physical nodes between the two modes of Kubernetes and SLURM orchestration as needed. On our HPC cluster, we use a public subnet for routing traffic to fileservers and outside and a private VLAN network switch/connection for PXE boot node provisioning only.
My question is the additional networking requirements for kubernetes cluster on physical nodes, do we need to present a separate private VLAN for the Weave Net pods networking toolkit?
Or are the Weave Net ip ranges reside on any physical server regardless of the networking switch VLAN configurations?
From my tests with VM, it seems like weavenet doesn’t really care about the actual networking VLAN presented to it. rather it creates its own based virtual network layer depending on the availability of the IP space. But I would like to get any confirmation on this from the community.
I hope this description is not too confusing… I would really appreciate any help on this.