Diagram
Here's a Mermaid network diagram representing your k3s cluster setup:
graph TD
subgraph Physical Machine 1
PM1_NIC[eth0 - 192.168.123.100] --> PM1_Bridge[br0]
PM1_Bridge -->|vmbr0| VM1[[VM1 - Master Node<br>192.168.123.221]]
PM1_Bridge -->|vmbr0| VM2[[VM2 - Worker Node<br>192.168.123.222]]
PM1_NFS[(NFS Server<br>/mnt/nfs-share)]
end
subgraph Physical Machine 2
PM2_NIC[eth0 - 192.168.123.230] --> PM2_Bridge[br0]
PM2_Bridge -->|vmbr0| VM3[[VM3 - Worker Node<br>192.168.123.223]]
end
VM1 -->|k3s API<br>6443/tcp| VM2
VM1 -->|k3s API<br>6443/tcp| VM3
VM2 -->|Flannel VXLAN<br>8472/udp| VM3
VM3 -->|Flannel VXLAN<br>8472/udp| VM1
VM1 -->|Flannel VXLAN<br>8472/udp| VM2
PM1_NFS -->|NFSv4<br>2049/tcp| VM1
PM1_NFS -->|NFSv4<br>2049/tcp| VM2
PM1_NFS -->|NFSv4<br>2049/tcp| VM3
classDef vm fill:#e1f5fe,stroke:#039be5,stroke-width:2px;
classDef physical fill:#f0f4c3,stroke:#9e9d24,stroke-width:2px;
classDef storage fill:#dcedc8,stroke:#689f38,stroke-width:2px;
class VM1,VM2,VM3 vm
class PM1_NIC,PM1_Bridge,PM2_NIC,PM2_Bridge physical
class PM1_NFS storage
style VM1 fill:#b3e5fc
style PM1_NFS fill:#c5e1a5
Key components shown:
- Two physical machines with bridge networking
- VM roles (Master/Worker) and their relationships
- NFS server location and connections
- Critical k3s communication ports
- Network interfaces and IP addressing scheme
- Flannel overlay network connections
The diagram shows:
- Master node (VM1) coordinating with worker nodes (VM2, VM3)
- NFS server mounted across all nodes
- Required network ports for cluster communication
- Bridge configurations for VM networking
- Different security zones for physical hosts and VMs