New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to initialize kubernetes cluster with assigned IP : Vagrant provisioned infra #69610

Open
irfanjs opened this Issue Oct 10, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@irfanjs

irfanjs commented Oct 10, 2018

Hello,

what is expected:
Kubernetes cluster should be initialized with custom network interface provisioned by vagrant.

How to reproduce :
Vagrant version : 2.1.4
oracle virtualbox version : Version 5.2.18 r124319 (Qt5.6.2)
Host OS : win 8.1 (64 bit), 8 GB RAM

two centos 7 boxes are provisioned. one is master and another is worker.
Using vagraantfile , able to create VM and was able to execute all commands successfully.

however, kubeadm init command always takes 10.x.x.x range IP address rather than the one which i provided in the script. (172.x.x.x)

i am not sure why this is happening and how kubernetes decides which network interface to pick up at the time of initialization.
i have gone to most k8s docs but never find the way to get it

here is the doc i referred for vagrant networking:
https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/
https://www.vagrantup.com/docs/virtualbox/networking.html

please suggest
Regards,

@irfanjs

This comment has been minimized.

Show comment
Hide comment
@irfanjs

irfanjs Oct 10, 2018

please suggest.
not getting , how kubernetes selects the network interfaces while initializing .....
as of now, it is selecting 10.x.x.x IP address ranges, but i need kubernetes to pick up 172.x.x.x ip address range. 172 ip address range is already available in enpS08 interface.

irfanjs commented Oct 10, 2018

please suggest.
not getting , how kubernetes selects the network interfaces while initializing .....
as of now, it is selecting 10.x.x.x IP address ranges, but i need kubernetes to pick up 172.x.x.x ip address range. 172 ip address range is already available in enpS08 interface.

@neolit123

This comment has been minimized.

Show comment
Hide comment
@neolit123

neolit123 Oct 11, 2018

Member

/triage support
/sig cluster-lifecycle

might be best to ask on slack in #kubeadm or in the support channels.
https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/

Member

neolit123 commented Oct 11, 2018

/triage support
/sig cluster-lifecycle

might be best to ask on slack in #kubeadm or in the support channels.
https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/

@irfanjs

This comment has been minimized.

Show comment
Hide comment
@irfanjs

irfanjs Oct 11, 2018

because of me in different timezone, most of the folks i see is offline ... so seeking suggestion here
please help

irfanjs commented Oct 11, 2018

because of me in different timezone, most of the folks i see is offline ... so seeking suggestion here
please help

@irfanjs

This comment has been minimized.

Show comment
Hide comment
@irfanjs

irfanjs Oct 12, 2018

this is resolved by using option : --apiserver-advertise-address along with --pod-network-cidr option

irfanjs commented Oct 12, 2018

this is resolved by using option : --apiserver-advertise-address along with --pod-network-cidr option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment