I tried to deploy a small test-cluster today. I noticed that despite the setting for a static IP the nameserver entries are deployed after the first update and package-install, which in my case failed. I haven't tested DHCP yet, but if the order of the script is the same (which i assume) the issue most likely is the same.
J
Offline
Posts
-
RE: Kubernetes Recipe VM failed to start - Raise Network Interfaces