I've got a cluster running with 1 master + 2 workers and using flannel as CNI.
kubeadm init was called with apiserver address and 10.244.0.0 for flannel's and nodes are joined.
kubeadm init --apiserver-advertise-address=192.168.56.3 --pod-network-cidr=10.244.0.0/16
NAME READY STATUS RESTARTS
coredns-f9fd979d6-d6jkd 1/1 Running 0
coredns-f9fd979d6-fpzct 1/1 Running 0
etcd-kubemaster 1/1 Running 0
kube-apiserver-kubemaster 1/1 Running 0
kube-controller-manager-kubemaster 1/1 Running 0
kube-flannel-ds-5gd2w 1/1 Running 0
kube-flannel-ds-b4qzz 1/1 Running 0
kube-flannel-ds-m56bd 1/1 Running 0
kube-proxy-5hw6x 1/1 Running 0
kube-proxy-9wnpd 1/1 Running 0
kube-proxy-ffrmh 1/1 Running 0
kube-scheduler-kubemaster 1/1 Running 0
iptables was cleared, everything allowed and net.bridge.bridge-nf-call-iptables=1
But the cluster cant be reached.
times out.
kubectl config view
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: DATA+OMITTED
server: https://192.168.56.3:6443
name: kubernetes
contexts:
- context:
cluster: kubernetes
user: kubernetes-admin
name: kubernetes-admin@kubernetes
current-context: kubernetes-admin@kubernetes
kind: Config
preferences: {}
users:
- name: kubernetes-admin
user:
client-certificate-data: REDACTED
client-key-data: REDACTED
What to do to get access to the cluster's services?