« Back to projectatomic.io
Ask Your Question

Kubernetes IP config

asked 2015-04-21 14:25:35 +0000

dsmithdewarcom gravatar image

My first go through the Getting Started guide has resulted in docker failure with ip addressing error messages

The guide gives the following "Assumptions for IP addressing"-- Physical interfaces for hosts: atomic-master kubernetes master atomic0[1-4][1-4] kubernetes minions Overlay Docker networking range:

The bridged ip of my vb instance is (confirmed externally by ip scanner), I swapped this in for "" (in the guide), and applied the empty ip's for KUBELET_ADDRESSES (I chose this range to avoid DHCP conflicts with physical devices on the subnet).

However "sudo systemctl status flanneld docker kubelet kube-proxy" is throwing "connection refused" to KUBE_MASTER

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-04-21 20:12:43 +0000

So your master is and your minion is

On the master, check to make sure the services are listening on the right ports with netstat -tnlp and make sure you can ping the minion

On the minion, check to see if you can hit the open port manually with curl -Ik and make sure you can ping the master

On both, check the version of kubernetes to see if you need the updated KUBE_MASTER syntax with rpm -q kubernetes

If you can capture the results that will help as well.

edit flag offensive delete link more


Are minions each run from a full-blown Atomic/other hypervisor installation, on a separate host instance?

dsmithdewarcom ( 2015-04-22 13:34:48 +0000 )edit

Yes, a minion is a complete separate Atomic install, on a new virutal guest.

nzwulfin ( 2015-04-22 15:15:11 +0000 )edit

OK. Thanks.

dsmithdewarcom ( 2015-04-22 16:03:33 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower


Asked: 2015-04-21 14:25:35 +0000

Seen: 249 times

Last updated: Apr 21 '15