Closed cprivitere closed 1 year ago
This works (rebased from main) and removes the potential risks of systemctl restart networking
. Even though we haven't seen those problems in a while (#9), so long as the network changes are simple enough to enact without a restart, this should be a good thing. If the network configuration we persist in files becomes more elaborate we may want to consider reverting back to systemctl commands.
root@eksa-g1dkz4-admin:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
147.75.88.147 Ready control-plane 13m v1.25.5-eks-c248520
147.75.88.148 Ready <none> 7m25s v1.25.5-eks-c248520
Update main and cloud-init to use ip addr add remove systemctl restart networking
fixes #9