is dhcp must forthe switches used in kubernetes install environment?

[Oğuz Yarımtepe]

Hi,

I am trying to install Kubernetes at my Baremetal nodes. The nodes have CoreOS installed and i have installed master node from https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/generic/controller-install.sh without errors. When i try adding the worker node i got the below error:

Aug 11 09:20:43 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:43.875024    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:43 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:43.875060    1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:44 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:44.913283    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:44 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:44.913337    1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:45 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:45.958095    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:45 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:45.958131    1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:47 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:47.002463    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:47 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:47.002490    1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:48 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:48.046091    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:48 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:48.046119    1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Service hold-off time over, scheduling restart.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: Stopped Cluster reboot manager.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: Started Cluster reboot manager.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Reboot strategy "best-effort" is deprecated and will be removed in the future.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Please explicitly set the reboot strategy to one of [off reboot etcd-lock]

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: See https://coreos.com/os/docs/latest/update-strategies.html for details on configuring reboot strategies.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: No configured reboot window

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Cannot get update engine status: The name com.coreos.update1 was not provided by any .service files

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Main process exited, code=exited, status=1/FAILURE

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Unit entered failed state.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Failed with result 'exit-code'.

Aug 11 09:20:49 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:49.091620    1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

I have dummy switches but no dhcp enabled? Can it a be the reason of the error? Any idea? Or any other non problamatic methos to install Kubernetes on Baremetal? The script has only 1.5.4 support it seems. I need to install the lates version also.

[Brandon Philips]

Hello Oğuz-

That guide is out of date and not maintained. I suggest you take a look at the Tectonic Installer for bare metal. 

Brandon

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Oğuz Yarımtepe]

Hi,

At last i tried tectonic bare metal installation. But i am not able to customize the POD and Service ip ranges at the GUI. Is there any known issue? I am using 1.7.1 installer. I have one master node two worker nodes waiting to be installed. Setup the deploy node. Havent enabled the PCE and DHCP at the network yet. Runnig the tectonic installer at my macos. 

Will be great if someone helps.

To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Oğuz Yarımtepe
http://about.me/oguzy

[Rob Szumski]

Hi there,

We are tracking a purely frontend bug that is related to custom CIDR ranges. You can work around this bug by using Terraform directly until we get a hotfix release out, or use an older version of the installer.

Have you used Terraform before? Here are the bare metal docs.

 - Rob

To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.

[Oğuz Yarımtepe]

I will try with the older version of tectonic first. Will inform about it. Never used Terraform.  Can be the backup plan.

Thank you.