Closed charleech closed 3 years ago
Full output of minikube logs
command:
After digging during the weekend, I've found that it is about the IP Address
of the Pod network
, 10.244.0.0/16
which may conflict with my internal network somewhere in the mist ! Then I try to find a way to change it so that I found the #9364 and #9838
I've changed the start up
command to the following and everything works like a charm.
minikube start --nodes 2 \
--docker-opt bip=172.18.0.1/16 \
--extra-config=kubeadm.pod-network-cidr=12.244.0.0/16
for i in `seq 1 10`; do curl http://192.168.49.2:31000; echo; done
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-hc4hn (12.244.1.3)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-hc4hn (12.244.1.3)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-5rxxf (12.244.0.2)
Hello from hello-695c67cf9c-hc4hn (12.244.1.3)
I'm not sure if there is any document mentioning about the --docker-opt bip=172.18.0.1/16
, --extra-config=kubeadm.pod-network-cidr=12.244.0.0/16
and other special additional parameters like them or not. Could you please help to advise further?
Could you please help to point me to the proper direction?
minikube version
minikube start --nodes 2 --docker-opt bip=172.18.0.1/16
minikube v1.21.0 on Centos 7.7.1908
Automatically selected the docker driver
Starting control plane node minikube in cluster minikube
Pulling base image ...
Downloading Kubernetes v1.20.7 preload ...
Creating docker container (CPUs=2, Memory=4000MB) ...
Preparing Kubernetes v1.20.7 on Docker 20.10.7 ...
Configuring CNI (Container Networking Interface) ...
Verifying Kubernetes components...
Enabled addons: storage-provisioner, default-storageclass
Starting node minikube-m02 in cluster minikube
Pulling base image ...
Creating docker container (CPUs=2, Memory=4000MB) ...
Found network options:
Preparing Kubernetes v1.20.7 on Docker 20.10.7 ...
Verifying Kubernetes components...
Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
I follow the example from https://minikube.sigs.k8s.io/docs/tutorials/multi_node/ by creating the
hello-svc.yaml
andhello-deployment.yaml
as the following: -Steps to reproduce the issue:
minikube delete --all --purge
minikube start --nodes 2 --docker-opt bip=172.18.0.1/16
kubectl get nodes
minikube status
minikube-m02 type: Worker host: Running kubelet: Running
deployment.apps/hello created
Waiting for deployment "hello" rollout to finish: 0 of 2 updated replicas are available... Waiting for deployment "hello" rollout to finish: 1 of 2 updated replicas are available... deployment "hello" successfully rolled out
service/hello created
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES hello-695c67cf9c-64b5z 1/1 Running 0 34s 10.244.1.2 minikube-m02
hello-695c67cf9c-q7dfx 1/1 Running 0 34s 10.244.0.3 minikube
for i in
seq 1 10
; do curl http://192.168.49.2:31000; echo; doneHello from hello-695c67cf9c-q7dfx (10.244.0.3) # <---- Only able to connect to node =
minikube
Hello from hello-695c67cf9c-q7dfx (10.244.0.3) curl: (28) Failed to connect to 192.168.49.2 port 31000: Connection timed out # <---- Is not able to connect to node =minikube-m02
Hello from hello-695c67cf9c-q7dfx (10.244.0.3) Hello from hello-695c67cf9c-q7dfx (10.244.0.3) curl: (28) Failed to connect to 192.168.49.2 port 31000: Connection timed out # <---- Is not able to connect to node =
minikube-m02
curl: (28) Failed to connect to 192.168.49.2 port 31000: Connection timed out # <---- Is not able to connect to node =
minikube-m02
Hello from hello-695c67cf9c-q7dfx (10.244.0.3) Hello from hello-695c67cf9c-q7dfx (10.244.0.3) Hello from hello-695c67cf9c-q7dfx (10.244.0.3)