Styjun

Are the definite and indefinite integrals actually two different things? Where is the flaw in my understanding?

Georgian capital letter “Ⴒ” (“tar”) in pdfLaTeX

Can I use ratchet straps to lift a dolly into a truck bed?

Dividing Divisive Divisors

Did Picard get in trouble when he was in command of the Stargazer and lost his ship?

Why are some Mac apps not available on AppStore?

Can I disable a battery powered device by reversing half of its batteries?

Which ping implementation is Cygwin using?

How do I improve my SXA sites Google PageSpeed Insights Score?

How to easily add discontinuity on x-axis?

Why should I always enable compiler warnings?

A Little Riddle

I changed a word from a source, how do I cite it correctly?

How seriously should I take a CBP interview where I was told I have a red flag and could only stay for 30 days?

Have there been any countries that voted themselves out of existence?

Why does F + F' = 1?

What is Japanese Language Stack Exchange called in Japanese?

Exact Brexit date and consequences

How to help my 2.5-year-old daughter take her medicine when she refuses to?

SharePoint 2013 with SQL 2012 License Query

Where does the expression "triple-A" comes from?

Is BitLocker useful in the case of stolen laptop?

How does Vivi differ from other Black Mages?

Is it possible to PIVOT on a LIKE statement

Kubernetes master node is not receiving internal IP

Kubernetes: kubectl node01 notreadykubernetes node not responding after restartKuberetes V1.6.2 flannel not running on master nodeDocker could not pull kubernetes related imageskubernetes cluster master node not readyunable to access kubernetes dashboard via tokenKubernetes Multi Master setupKube-Flannel cant get CIDR although PodCIDR available on nodeFailure Err: Not able to connect to any etcd endpoints - etcd: 0/1 connected: kubeadmKubernetes - does not start the role of master

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

I have followed the official guides and started a simple 3 node cluster, however
the command kubeadm get nodes -o wide prints this result:

NAME STATUS ROLES AGE VERSION INTERNAL-IP 
node2 Ready master 12h v1.13.4 <none>
node3 Ready <none> 12h v1.13.4 192.168.1.47 
node4 Ready <none> 12h v1.13.4 192.168.1.48

Please not the INTERNAL-IP of node2 (which is master node).

Because of that, pods that are on node2 do not receive an IP, even though all of them are system pods.

Environment:

1. Network: VirtualBox bridged adabter no NAT whatsoever


2. Network plugin: Flannel
   


3. OS: Ubuntu 18.04 LTS

Update

Here is the output of kubectl get pods -n kube-system as requested in comments:

NAME STATUS IP NODE 
coredns-86c58d9df4-d2dv7 Running 10.244.0.52 node2
coredns-86c58d9df4-zwmzg Running 10.244.0.51 node2
etcd-node2 Running <none> node2
kube-apiserver-node2 Running <none> node2
kube-controller-manr-node2 Running <none> node2
kube-flannel-ds-amd64-5dpr9 Running 192.168.1.47 node3
kube-flannel-ds-amd64-97h5q Running <none> node2
kube-flannel-ds-amd64-zwlxh Running 192.168.1.48 node4
kube-proxy-4qlpc Running <none> node2
kube-proxy-c28q9 Running 192.168.1.48 node4
kube-proxy-ntdxj Running 192.168.1.47 node3
kube-scheduler-node2 Running <none> node2

pods on master are also getting <none>.

Also i have created a gist for kubectl describe node node2 here

kubernetes flannel

share|improve this question

edited Mar 28 at 13:34

SHM

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  share the output from kubectl get po -n kube-system
  
  – P Ekambaram
  Mar 28 at 11:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  also please share kubectl describe node node2 output
  
  – A_Suh
  Mar 28 at 12:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Added pods and node info.
  
  – SHM
  Mar 28 at 13:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Do you see any IP related errors with journalctl -u kubelet -f -l ?
  
  – char
  Apr 12 at 8:10
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What kubeadm init flags did you used to start your cluster? I'm seeing a potential mismatch in your pods subnets (10.244.x.x vs 192.168.x.x). As per Installing a pod network add-on, for Flannel to work correctly, you must pass --pod-network-cidr=10.244.0.0/16 to kubeadm init.
  
  – Eduardo Baitello
  Apr 18 at 12:02
  

  
  
  
  

add a comment | 

0

I have followed the official guides and started a simple 3 node cluster, however
the command kubeadm get nodes -o wide prints this result:

NAME STATUS ROLES AGE VERSION INTERNAL-IP 
node2 Ready master 12h v1.13.4 <none>
node3 Ready <none> 12h v1.13.4 192.168.1.47 
node4 Ready <none> 12h v1.13.4 192.168.1.48

Please not the INTERNAL-IP of node2 (which is master node).

Because of that, pods that are on node2 do not receive an IP, even though all of them are system pods.

Environment:

1. Network: VirtualBox bridged adabter no NAT whatsoever


2. Network plugin: Flannel
   


3. OS: Ubuntu 18.04 LTS

Update

Here is the output of kubectl get pods -n kube-system as requested in comments:

NAME STATUS IP NODE 
coredns-86c58d9df4-d2dv7 Running 10.244.0.52 node2
coredns-86c58d9df4-zwmzg Running 10.244.0.51 node2
etcd-node2 Running <none> node2
kube-apiserver-node2 Running <none> node2
kube-controller-manr-node2 Running <none> node2
kube-flannel-ds-amd64-5dpr9 Running 192.168.1.47 node3
kube-flannel-ds-amd64-97h5q Running <none> node2
kube-flannel-ds-amd64-zwlxh Running 192.168.1.48 node4
kube-proxy-4qlpc Running <none> node2
kube-proxy-c28q9 Running 192.168.1.48 node4
kube-proxy-ntdxj Running 192.168.1.47 node3
kube-scheduler-node2 Running <none> node2

pods on master are also getting <none>.

Also i have created a gist for kubectl describe node node2 here

kubernetes flannel

share|improve this question

edited Mar 28 at 13:34

SHM

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  share the output from kubectl get po -n kube-system
  
  – P Ekambaram
  Mar 28 at 11:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  also please share kubectl describe node node2 output
  
  – A_Suh
  Mar 28 at 12:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Added pods and node info.
  
  – SHM
  Mar 28 at 13:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Do you see any IP related errors with journalctl -u kubelet -f -l ?
  
  – char
  Apr 12 at 8:10
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What kubeadm init flags did you used to start your cluster? I'm seeing a potential mismatch in your pods subnets (10.244.x.x vs 192.168.x.x). As per Installing a pod network add-on, for Flannel to work correctly, you must pass --pod-network-cidr=10.244.0.0/16 to kubeadm init.
  
  – Eduardo Baitello
  Apr 18 at 12:02
  

  
  
  
  

add a comment | 

I have followed the official guides and started a simple 3 node cluster, however
the command kubeadm get nodes -o wide prints this result:

NAME STATUS ROLES AGE VERSION INTERNAL-IP 
node2 Ready master 12h v1.13.4 <none>
node3 Ready <none> 12h v1.13.4 192.168.1.47 
node4 Ready <none> 12h v1.13.4 192.168.1.48

Please not the INTERNAL-IP of node2 (which is master node).

Because of that, pods that are on node2 do not receive an IP, even though all of them are system pods.

Environment:

1. Network: VirtualBox bridged adabter no NAT whatsoever


2. Network plugin: Flannel
   


3. OS: Ubuntu 18.04 LTS

Update

Here is the output of kubectl get pods -n kube-system as requested in comments:

NAME STATUS IP NODE 
coredns-86c58d9df4-d2dv7 Running 10.244.0.52 node2
coredns-86c58d9df4-zwmzg Running 10.244.0.51 node2
etcd-node2 Running <none> node2
kube-apiserver-node2 Running <none> node2
kube-controller-manr-node2 Running <none> node2
kube-flannel-ds-amd64-5dpr9 Running 192.168.1.47 node3
kube-flannel-ds-amd64-97h5q Running <none> node2
kube-flannel-ds-amd64-zwlxh Running 192.168.1.48 node4
kube-proxy-4qlpc Running <none> node2
kube-proxy-c28q9 Running 192.168.1.48 node4
kube-proxy-ntdxj Running 192.168.1.47 node3
kube-scheduler-node2 Running <none> node2

pods on master are also getting <none>.

Also i have created a gist for kubectl describe node node2 here

kubernetes flannel

share|improve this question

edited Mar 28 at 13:34

SHM

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

NAME STATUS ROLES AGE VERSION INTERNAL-IP 
node2 Ready master 12h v1.13.4 <none>
node3 Ready <none> 12h v1.13.4 192.168.1.47 
node4 Ready <none> 12h v1.13.4 192.168.1.48

NAME STATUS IP NODE 
coredns-86c58d9df4-d2dv7 Running 10.244.0.52 node2
coredns-86c58d9df4-zwmzg Running 10.244.0.51 node2
etcd-node2 Running <none> node2
kube-apiserver-node2 Running <none> node2
kube-controller-manr-node2 Running <none> node2
kube-flannel-ds-amd64-5dpr9 Running 192.168.1.47 node3
kube-flannel-ds-amd64-97h5q Running <none> node2
kube-flannel-ds-amd64-zwlxh Running 192.168.1.48 node4
kube-proxy-4qlpc Running <none> node2
kube-proxy-c28q9 Running 192.168.1.48 node4
kube-proxy-ntdxj Running 192.168.1.47 node3
kube-scheduler-node2 Running <none> node2

kubernetes flannel

kubernetes flannel

share|improve this question

edited Mar 28 at 13:34

SHM

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

share|improve this question

edited Mar 28 at 13:34

SHM

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges

asked Mar 28 at 8:53

SHMSHM

1,1591212 silver badges2929 bronze badges