The k8svagrantcluster from colby

colby / k8svagrantcluster Goto Github PK

View Code? Open in Web Editor NEW

"Bare Metal" Kubernetes cluster with Vagrant, Flannel, and MetalLB.

License: GNU General Public License v3.0

Ruby 73.13% HTML 7.76% Dockerfile 2.30% Shell 16.81%

k8svagrantcluster's People

Contributors

Stargazers

Watchers

k8svagrantcluster's Issues

Flannel failures after changing kubeadm init

Slave nodes (s1 and s2) are failing to run flannel pods after initializing k8s cluster using kubeadm init --config=kubeadm-config.yaml.

kubeadm-config.yaml

apiServer:
  certSANs:
  - "10.10.3.5"
apiVersion: kubeadm.k8s.io/v1beta1
certificatesDir: /etc/kubernetes/pki
controlPlaneEndpoint: "10.10.3.5:6443"
imageRepository: k8s.gcr.io
kind: ClusterConfiguration
kubernetesVersion: stable
networking:
  podSubnet: "10.244.0.0/16"

flannel pod failure

kube@m1:~$ kubectl logs kube-flannel-ds-amd64-lqxbx --namespace=kube-system
I0225 18:00:45.313462       1 main.go:488] Using interface with name enp0s8 and address 10.10.3.21
I0225 18:00:45.313524       1 main.go:505] Defaulting external address to interface address (10.10.3.21)
E0225 18:00:45.314295       1 main.go:232] Failed to create SubnetManager: error retrieving pod spec for 'kube-system/kube-flannel-ds-amd64-lqxbx': Get https://10.96.0.1:443/api/v1/namespaces/kube-system/pods
/kube-flannel-ds-amd64-lqxbx: dial tcp 10.96.0.1:443: getsockopt: connection refused

Recommend Projects