1-Background
The idea could be split into two parts: fixed IP and splitted network.
- For fixed IP, when power supply cut off in lab, machine will reboot, causing DHCP IP re-allocation, changed IP makes k8s system running into failure, re-deploy will be needed and time wasted.
- For splitted network, one is from secutiry point of view, management network allows root ssh login, but the cluster network does not need such priviledge when network note splitted, there’ll be secutiry concerns; another idea is for throughput consideration, cluster network will require more throughput, but management network may needs less than that, e.g. storage application could use cluster network, sharing network is not a good idea.
2-Topo (VMs)
2-Modifications
- Adding parameter for kubeadm:
--apiserver-advertise-address=192.168.123.162
3-Good to know
Action will build from base url, could use this feature to create different sub domain under github.io. e.g. create a repo called projects to display different projects, this will be added to github.io/prjects
If site deployment is automatically triggered by Github Action, need to notice the time difference between Github server and local time zone.
Opens
- For cluster network, how to cope with other CNIs?
- How to detect interface by IP/subnets?
- not tested for multi-etcd
Reference
1-https://gohugo.io/hosting-and-deployment/hosting-on-github/
2-https://lucumt.info/post/hugo/using-github-action-to-auto-build-deploy/