Access
The kubernetes cluster sits behind a Gateway Device on the home network and is assigned a DHCP address. The kube user is located on the control-plane node.
k8s Cluster
#> ssh ubuntu@192.168.1.xxx (Gateway Device)
#> ssh ubuntu@k8s-control-plane-node
#> sudo su - kube
#> kubectl get nodes
kube@k8s-control-plane-node:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-control-plane-node Ready control-plane 10d v1.25.5
k8s-node2 Ready <none> 10d v1.25.5
...
Note: 192.168.1.xxx (Gateway Device) is the IP Address of the Gateway Device given out by the Home Network. More details: Home Network DNS
Networking
This project uses a gateway device to support a local subnet. The subnet reaches the WWW via this gateway device and uses various network services such as DNS running on this gateway.
- LAN domain: cluster.home
- Docker Registry: registry.cluster.home
- Flamenco Manager: flamenco.cluster.home
- NFS: nfs.cluster.home
- External LB: 192.168.57.200 (services.cluster.home)
- Gateway Device / Gateway Server gateway 192.168.57.30 (gateway.cluster.home)
Kubernetes Nodes
Current list of known k8s nodes:
Address | Hostname | Hardware | k8s Role |
---|---|---|---|
192.168.57.31 | k8s-control-plane-node.cluster.home | beelink U59 celeron | Control-Plane |
192.168.57.32 | k8s-node2.cluster.home | intel nuc i5 | Worker |
192.168.57.33 | k8s-node3.cluster.home | intel nuc i5 | Worker |
192.168.57.34 | k8s-node4.cluster.home | intel nuc i5 | Worker |
192.168.57.35 | k8s-node5.cluster.home | intel nuc i5 | Worker |
192.168.57.36 | k8s-node6.cluster.home | lenovo thinkcentre M910q i7 | Worker |
192.168.57.37 | k8s-node7.cluster.home | lenovo thinkcentre M910q i7 | Worker |
192.168.57.38 | k8s-node8.cluster.home | lenovo thinkcentre M910q i7 | Worker |
192.168.57.39 | k8s-node9.cluster.home | lenovo thinkcentre M910x i7 | Worker |
192.168.57.40 | k8s-node10.cluster.home | lenovo thinkcentre M910q i7 | Worker |
192.168.57.41 | k8s-node11.cluster.home | lenovo thinkcentre M910q i7 | Worker |
Wake On Lan
This project will create wake-on-lan scripts for all known nodes.
For more details see Use Cases/Powering Up Cluster
(auto-generated file)