Diagram
graph TD;
A[Physical Machine 1<br>192.168.123.100] -->|VM1<br>192.168.123.221| B["Master Node (k3s Server)"]
A -->|VM2<br>192.168.123.222| C["Worker Node (k3s Agent)"]
D[Physical Machine 2<br>192.168.123.230] -->|VM3<br>192.168.123.223| E["Worker Node (k3s Agent)"]
subgraph NFS
F[NFS Share]
end
B -->|Kubernetes API| C
B -->|Kubernetes API| E
F -->|NFS Mount| B
F -->|NFS Mount| C
F -->|NFS Mount| E
style A fill:#f9f,stroke:#333,stroke-width:2px;
style D fill:#f9f,stroke:#333,stroke-width:2px;
style B fill:#bbf,stroke:#333,stroke-width:2px;
style C fill:#bbf,stroke:#333,stroke-width:2px;
style E fill:#bbf,stroke:#333,stroke-width:2px;
style F fill:#ffb,stroke:#333,stroke-width:2px;
Explanation of the Diagram:
-
Physical Machine 1 hosts two VMs:
- VM1: Master Node (k3s Server)
- VM2: Worker Node (k3s Agent)
-
Physical Machine 2 hosts:
- VM3: Worker Node (k3s Agent)
-
The NFS Share is accessible from all three VMs, providing persistent storage for the applications deployed in the Kubernetes cluster.
-
The arrows indicate the communication paths:
- The Master Node communicates with both Worker Nodes via the Kubernetes API.
- Each node mounts the NFS share for persistent storage.
You can copy and paste the above Mermaid code into a compatible viewer to visualize the network diagram.