Can join the cluster, but unable to fetch kubeadm-confighow do i get the minikube nodes in a local clusterAccessing local GAE SDK server from another computer in the networkHow to set the localhost of the VM machine identical to the host computer?kubeadm join failing. Unable to request signed certkubernetes dial tcp i/o timeout error in version 1.7.0. Also kubeadm join command failsCreating HA clusters with kubeadmPods on different nodes can't ping each otherBuilding a Bare Metal Kubernetes Cluster with kubeadmKubeadm init configuration for the Kubernetes ClusterDeploy Neo4j cluster with kubernetes kubeadmHow to expose a web app on a kubeadm cluster?

One verb to replace 'be a member of' a club

Assassin's bullet with mercury

Little known, relatively unlikely, but scientifically plausible, apocalyptic (or near apocalyptic) events

Is it inappropriate for a student to attend their mentor's dissertation defense?

How can saying a song's name be a copyright violation?

Forgetting the musical notes while performing in concert

How badly should I try to prevent a user from XSSing themselves?

What killed these X2 caps?

Watching something be piped to a file live with tail

How would I stat a creature to be immune to everything but the Magic Missile spell? (just for fun)

Could the museum Saturn V's be refitted for one more flight?

How do I gain back my faith in my PhD degree?

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

Do UK voters know if their MP will be the Speaker of the House?

Why can't we play rap on piano?

Would Slavery Reparations be considered Bills of Attainder and hence Illegal?

GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

Detention in 1997

Is it possible to create a QR code using text?

Avoiding direct proof while writing proof by induction

Alternative to sending password over mail?

Examples of smooth manifolds admitting inbetween one and a continuum of complex structures

What are some good books on Machine Learning and AI like Krugman, Wells and Graddy's "Essentials of Economics"



Can join the cluster, but unable to fetch kubeadm-config


how do i get the minikube nodes in a local clusterAccessing local GAE SDK server from another computer in the networkHow to set the localhost of the VM machine identical to the host computer?kubeadm join failing. Unable to request signed certkubernetes dial tcp i/o timeout error in version 1.7.0. Also kubeadm join command failsCreating HA clusters with kubeadmPods on different nodes can't ping each otherBuilding a Bare Metal Kubernetes Cluster with kubeadmKubeadm init configuration for the Kubernetes ClusterDeploy Neo4j cluster with kubernetes kubeadmHow to expose a web app on a kubeadm cluster?













0















I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes.



master names minikube.



$ kubeadm version
kubeadm version: &version.InfoMajor:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"
$ kubelet --version
Kubernetes v1.13.3


login to the minikube console by
minikube ssh



Then check the ip addresses with ifconfig



$ ifconfig
docker0 Link encap:Ethernet HWaddr 02:42:0E:E5:B4:9C
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:eff:fee5:b49c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18727 errors:0 dropped:0 overruns:0 frame:0
TX packets:21337 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1621416 (1.5 MiB) TX bytes:6858635 (6.5 MiB)

eth0 Link encap:Ethernet HWaddr 08:00:27:04:9E:5F
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe04:9e5f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:139646 errors:0 dropped:0 overruns:0 frame:0
TX packets:11964 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:202559446 (193.1 MiB) TX bytes:996669 (973.3 KiB)

eth1 Link encap:Ethernet HWaddr 08:00:27:10:7A:A5
inet addr:192.168.99.105 Bcast:192.168.99.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe10:7aa5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2317 errors:0 dropped:0 overruns:0 frame:0
TX packets:2231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:197781 (193.1 KiB) TX bytes:199788 (195.1 KiB)


Therefore my minikube ip address is 192.168.99.105



On my VM node. I have checked that they are using the same network.
Networks are



  1. NAT


  2. Host-only Adapter Names:vboxnet0`


Here is the nmap proof that no firewall against connection port
enter image description here



Execute the kubeadm join to join the cluster.
If it get the exact output from cli. It is even worse. Because the command output is calling the localhost and when it comes to the executor it means it calls itself which is wrong and therefore after execute it. Terminial will show me timeout error



kubeadm join 192.168.99.105:8443 --token 856tch.tpccuji4nnc2zq5g --discovery-token-ca-cert-hash sha256:cfbb7a0f9ed7fca018b45fdfecb753a88aec64d4e46b5ac9ceb6d04bbb0a46a6


kubeadm show me localhost back!
enter image description here



Surly I did not get any node



$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 104m v1.13.3


Question:



  1. How to let kubeadm follow my given ip address in the cli correctly?


  2. How to prevent localhost come back during the process?










share|improve this question




























    0















    I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes.



    master names minikube.



    $ kubeadm version
    kubeadm version: &version.InfoMajor:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"
    $ kubelet --version
    Kubernetes v1.13.3


    login to the minikube console by
    minikube ssh



    Then check the ip addresses with ifconfig



    $ ifconfig
    docker0 Link encap:Ethernet HWaddr 02:42:0E:E5:B4:9C
    inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
    inet6 addr: fe80::42:eff:fee5:b49c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:18727 errors:0 dropped:0 overruns:0 frame:0
    TX packets:21337 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1621416 (1.5 MiB) TX bytes:6858635 (6.5 MiB)

    eth0 Link encap:Ethernet HWaddr 08:00:27:04:9E:5F
    inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe04:9e5f/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:139646 errors:0 dropped:0 overruns:0 frame:0
    TX packets:11964 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:202559446 (193.1 MiB) TX bytes:996669 (973.3 KiB)

    eth1 Link encap:Ethernet HWaddr 08:00:27:10:7A:A5
    inet addr:192.168.99.105 Bcast:192.168.99.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe10:7aa5/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2317 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2231 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:197781 (193.1 KiB) TX bytes:199788 (195.1 KiB)


    Therefore my minikube ip address is 192.168.99.105



    On my VM node. I have checked that they are using the same network.
    Networks are



    1. NAT


    2. Host-only Adapter Names:vboxnet0`


    Here is the nmap proof that no firewall against connection port
    enter image description here



    Execute the kubeadm join to join the cluster.
    If it get the exact output from cli. It is even worse. Because the command output is calling the localhost and when it comes to the executor it means it calls itself which is wrong and therefore after execute it. Terminial will show me timeout error



    kubeadm join 192.168.99.105:8443 --token 856tch.tpccuji4nnc2zq5g --discovery-token-ca-cert-hash sha256:cfbb7a0f9ed7fca018b45fdfecb753a88aec64d4e46b5ac9ceb6d04bbb0a46a6


    kubeadm show me localhost back!
    enter image description here



    Surly I did not get any node



    $ kubectl get nodes
    NAME STATUS ROLES AGE VERSION
    minikube Ready master 104m v1.13.3


    Question:



    1. How to let kubeadm follow my given ip address in the cli correctly?


    2. How to prevent localhost come back during the process?










    share|improve this question


























      0












      0








      0








      I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes.



      master names minikube.



      $ kubeadm version
      kubeadm version: &version.InfoMajor:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"
      $ kubelet --version
      Kubernetes v1.13.3


      login to the minikube console by
      minikube ssh



      Then check the ip addresses with ifconfig



      $ ifconfig
      docker0 Link encap:Ethernet HWaddr 02:42:0E:E5:B4:9C
      inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
      inet6 addr: fe80::42:eff:fee5:b49c/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:18727 errors:0 dropped:0 overruns:0 frame:0
      TX packets:21337 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:1621416 (1.5 MiB) TX bytes:6858635 (6.5 MiB)

      eth0 Link encap:Ethernet HWaddr 08:00:27:04:9E:5F
      inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe04:9e5f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:139646 errors:0 dropped:0 overruns:0 frame:0
      TX packets:11964 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:202559446 (193.1 MiB) TX bytes:996669 (973.3 KiB)

      eth1 Link encap:Ethernet HWaddr 08:00:27:10:7A:A5
      inet addr:192.168.99.105 Bcast:192.168.99.255 Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe10:7aa5/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:2317 errors:0 dropped:0 overruns:0 frame:0
      TX packets:2231 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:197781 (193.1 KiB) TX bytes:199788 (195.1 KiB)


      Therefore my minikube ip address is 192.168.99.105



      On my VM node. I have checked that they are using the same network.
      Networks are



      1. NAT


      2. Host-only Adapter Names:vboxnet0`


      Here is the nmap proof that no firewall against connection port
      enter image description here



      Execute the kubeadm join to join the cluster.
      If it get the exact output from cli. It is even worse. Because the command output is calling the localhost and when it comes to the executor it means it calls itself which is wrong and therefore after execute it. Terminial will show me timeout error



      kubeadm join 192.168.99.105:8443 --token 856tch.tpccuji4nnc2zq5g --discovery-token-ca-cert-hash sha256:cfbb7a0f9ed7fca018b45fdfecb753a88aec64d4e46b5ac9ceb6d04bbb0a46a6


      kubeadm show me localhost back!
      enter image description here



      Surly I did not get any node



      $ kubectl get nodes
      NAME STATUS ROLES AGE VERSION
      minikube Ready master 104m v1.13.3


      Question:



      1. How to let kubeadm follow my given ip address in the cli correctly?


      2. How to prevent localhost come back during the process?










      share|improve this question
















      I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes.



      master names minikube.



      $ kubeadm version
      kubeadm version: &version.InfoMajor:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"
      $ kubelet --version
      Kubernetes v1.13.3


      login to the minikube console by
      minikube ssh



      Then check the ip addresses with ifconfig



      $ ifconfig
      docker0 Link encap:Ethernet HWaddr 02:42:0E:E5:B4:9C
      inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
      inet6 addr: fe80::42:eff:fee5:b49c/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:18727 errors:0 dropped:0 overruns:0 frame:0
      TX packets:21337 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:1621416 (1.5 MiB) TX bytes:6858635 (6.5 MiB)

      eth0 Link encap:Ethernet HWaddr 08:00:27:04:9E:5F
      inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe04:9e5f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:139646 errors:0 dropped:0 overruns:0 frame:0
      TX packets:11964 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:202559446 (193.1 MiB) TX bytes:996669 (973.3 KiB)

      eth1 Link encap:Ethernet HWaddr 08:00:27:10:7A:A5
      inet addr:192.168.99.105 Bcast:192.168.99.255 Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe10:7aa5/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:2317 errors:0 dropped:0 overruns:0 frame:0
      TX packets:2231 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:197781 (193.1 KiB) TX bytes:199788 (195.1 KiB)


      Therefore my minikube ip address is 192.168.99.105



      On my VM node. I have checked that they are using the same network.
      Networks are



      1. NAT


      2. Host-only Adapter Names:vboxnet0`


      Here is the nmap proof that no firewall against connection port
      enter image description here



      Execute the kubeadm join to join the cluster.
      If it get the exact output from cli. It is even worse. Because the command output is calling the localhost and when it comes to the executor it means it calls itself which is wrong and therefore after execute it. Terminial will show me timeout error



      kubeadm join 192.168.99.105:8443 --token 856tch.tpccuji4nnc2zq5g --discovery-token-ca-cert-hash sha256:cfbb7a0f9ed7fca018b45fdfecb753a88aec64d4e46b5ac9ceb6d04bbb0a46a6


      kubeadm show me localhost back!
      enter image description here



      Surly I did not get any node



      $ kubectl get nodes
      NAME STATUS ROLES AGE VERSION
      minikube Ready master 104m v1.13.3


      Question:



      1. How to let kubeadm follow my given ip address in the cli correctly?


      2. How to prevent localhost come back during the process?







      kubernetes localhost kubectl minikube kubeadm






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 16 at 7:01







      Sarit

















      asked Mar 15 at 9:18









      SaritSarit

      1,53721943




      1,53721943






















          2 Answers
          2






          active

          oldest

          votes


















          0














          On step 2, you should run this command:




          kubeadm token create --print-join-command




          That should provide the exact syntax you need to add a worker node to your cluster. Don't change anything






          share|improve this answer























          • Thanks for sharing. Please check my updated question.

            – Sarit
            Mar 16 at 7:02


















          0














          This seems to be an issue with current Minikube code, which I guess changed since the post was made.
          Take a look at https://github.com/kubernetes/minikube/issues/3916.
          I've managed to join a second node by DNATting 127.0.0.1:8443 to the original minikube master.



          Just FTR, I added a /etc/rc.local at the second node with:
          (replace LOCAL_IF, MASTER_IP and WORKER_IP with sensible data)



          #!/bin/sh
          echo 1 > /proc/sys/net/ipv4/conf/<LOCAL_IF>/route_localnet
          /sbin/iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --destination-port
          8443 -j DNAT --to-destination <MASTER_IP>:8443
          /sbin/iptables -t nat -A POSTROUTING -p tcp -s 127.0.0.1 -d <MASTER_IP>
          --dport 8443 -j SNAT --to <WORKER_IP>


          But problems did not end there. Installing flannel with:



          kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml


          worked (after allocating node CIDRs via controller manager), but my second node somehow had a different kubelet installation, that installed cni as network plugin, and ended up creating a new bridge (cni0) that clashed with docker network.



          There are many things that have to work together for this to fly.






          share|improve this answer

























          • Thanks for sharing. I will be back to this question again.

            – Sarit
            Mar 22 at 4:15











          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55179194%2fcan-join-the-cluster-but-unable-to-fetch-kubeadm-config%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          On step 2, you should run this command:




          kubeadm token create --print-join-command




          That should provide the exact syntax you need to add a worker node to your cluster. Don't change anything






          share|improve this answer























          • Thanks for sharing. Please check my updated question.

            – Sarit
            Mar 16 at 7:02















          0














          On step 2, you should run this command:




          kubeadm token create --print-join-command




          That should provide the exact syntax you need to add a worker node to your cluster. Don't change anything






          share|improve this answer























          • Thanks for sharing. Please check my updated question.

            – Sarit
            Mar 16 at 7:02













          0












          0








          0







          On step 2, you should run this command:




          kubeadm token create --print-join-command




          That should provide the exact syntax you need to add a worker node to your cluster. Don't change anything






          share|improve this answer













          On step 2, you should run this command:




          kubeadm token create --print-join-command




          That should provide the exact syntax you need to add a worker node to your cluster. Don't change anything







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 16 at 1:33









          tenboschtenbosch

          12




          12












          • Thanks for sharing. Please check my updated question.

            – Sarit
            Mar 16 at 7:02

















          • Thanks for sharing. Please check my updated question.

            – Sarit
            Mar 16 at 7:02
















          Thanks for sharing. Please check my updated question.

          – Sarit
          Mar 16 at 7:02





          Thanks for sharing. Please check my updated question.

          – Sarit
          Mar 16 at 7:02













          0














          This seems to be an issue with current Minikube code, which I guess changed since the post was made.
          Take a look at https://github.com/kubernetes/minikube/issues/3916.
          I've managed to join a second node by DNATting 127.0.0.1:8443 to the original minikube master.



          Just FTR, I added a /etc/rc.local at the second node with:
          (replace LOCAL_IF, MASTER_IP and WORKER_IP with sensible data)



          #!/bin/sh
          echo 1 > /proc/sys/net/ipv4/conf/<LOCAL_IF>/route_localnet
          /sbin/iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --destination-port
          8443 -j DNAT --to-destination <MASTER_IP>:8443
          /sbin/iptables -t nat -A POSTROUTING -p tcp -s 127.0.0.1 -d <MASTER_IP>
          --dport 8443 -j SNAT --to <WORKER_IP>


          But problems did not end there. Installing flannel with:



          kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml


          worked (after allocating node CIDRs via controller manager), but my second node somehow had a different kubelet installation, that installed cni as network plugin, and ended up creating a new bridge (cni0) that clashed with docker network.



          There are many things that have to work together for this to fly.






          share|improve this answer

























          • Thanks for sharing. I will be back to this question again.

            – Sarit
            Mar 22 at 4:15















          0














          This seems to be an issue with current Minikube code, which I guess changed since the post was made.
          Take a look at https://github.com/kubernetes/minikube/issues/3916.
          I've managed to join a second node by DNATting 127.0.0.1:8443 to the original minikube master.



          Just FTR, I added a /etc/rc.local at the second node with:
          (replace LOCAL_IF, MASTER_IP and WORKER_IP with sensible data)



          #!/bin/sh
          echo 1 > /proc/sys/net/ipv4/conf/<LOCAL_IF>/route_localnet
          /sbin/iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --destination-port
          8443 -j DNAT --to-destination <MASTER_IP>:8443
          /sbin/iptables -t nat -A POSTROUTING -p tcp -s 127.0.0.1 -d <MASTER_IP>
          --dport 8443 -j SNAT --to <WORKER_IP>


          But problems did not end there. Installing flannel with:



          kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml


          worked (after allocating node CIDRs via controller manager), but my second node somehow had a different kubelet installation, that installed cni as network plugin, and ended up creating a new bridge (cni0) that clashed with docker network.



          There are many things that have to work together for this to fly.






          share|improve this answer

























          • Thanks for sharing. I will be back to this question again.

            – Sarit
            Mar 22 at 4:15













          0












          0








          0







          This seems to be an issue with current Minikube code, which I guess changed since the post was made.
          Take a look at https://github.com/kubernetes/minikube/issues/3916.
          I've managed to join a second node by DNATting 127.0.0.1:8443 to the original minikube master.



          Just FTR, I added a /etc/rc.local at the second node with:
          (replace LOCAL_IF, MASTER_IP and WORKER_IP with sensible data)



          #!/bin/sh
          echo 1 > /proc/sys/net/ipv4/conf/<LOCAL_IF>/route_localnet
          /sbin/iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --destination-port
          8443 -j DNAT --to-destination <MASTER_IP>:8443
          /sbin/iptables -t nat -A POSTROUTING -p tcp -s 127.0.0.1 -d <MASTER_IP>
          --dport 8443 -j SNAT --to <WORKER_IP>


          But problems did not end there. Installing flannel with:



          kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml


          worked (after allocating node CIDRs via controller manager), but my second node somehow had a different kubelet installation, that installed cni as network plugin, and ended up creating a new bridge (cni0) that clashed with docker network.



          There are many things that have to work together for this to fly.






          share|improve this answer















          This seems to be an issue with current Minikube code, which I guess changed since the post was made.
          Take a look at https://github.com/kubernetes/minikube/issues/3916.
          I've managed to join a second node by DNATting 127.0.0.1:8443 to the original minikube master.



          Just FTR, I added a /etc/rc.local at the second node with:
          (replace LOCAL_IF, MASTER_IP and WORKER_IP with sensible data)



          #!/bin/sh
          echo 1 > /proc/sys/net/ipv4/conf/<LOCAL_IF>/route_localnet
          /sbin/iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --destination-port
          8443 -j DNAT --to-destination <MASTER_IP>:8443
          /sbin/iptables -t nat -A POSTROUTING -p tcp -s 127.0.0.1 -d <MASTER_IP>
          --dport 8443 -j SNAT --to <WORKER_IP>


          But problems did not end there. Installing flannel with:



          kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml


          worked (after allocating node CIDRs via controller manager), but my second node somehow had a different kubelet installation, that installed cni as network plugin, and ended up creating a new bridge (cni0) that clashed with docker network.



          There are many things that have to work together for this to fly.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 22 at 21:31

























          answered Mar 21 at 21:07









          Carlos MendiorozCarlos Mendioroz

          11




          11












          • Thanks for sharing. I will be back to this question again.

            – Sarit
            Mar 22 at 4:15

















          • Thanks for sharing. I will be back to this question again.

            – Sarit
            Mar 22 at 4:15
















          Thanks for sharing. I will be back to this question again.

          – Sarit
          Mar 22 at 4:15





          Thanks for sharing. I will be back to this question again.

          – Sarit
          Mar 22 at 4:15

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55179194%2fcan-join-the-cluster-but-unable-to-fetch-kubeadm-config%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

          Swift 4 - func physicsWorld not invoked on collision? The Next CEO of Stack OverflowHow to call Objective-C code from Swift#ifdef replacement in the Swift language@selector() in Swift?#pragma mark in Swift?Swift for loop: for index, element in array?dispatch_after - GCD in Swift?Swift Beta performance: sorting arraysSplit a String into an array in Swift?The use of Swift 3 @objc inference in Swift 4 mode is deprecated?How to optimize UITableViewCell, because my UITableView lags

          Access current req object everywhere in Node.js ExpressWhy are global variables considered bad practice? (node.js)Using req & res across functionsHow do I get the path to the current script with Node.js?What is Node.js' Connect, Express and “middleware”?Node.js w/ express error handling in callbackHow to access the GET parameters after “?” in Express?Modify Node.js req object parametersAccess “app” variable inside of ExpressJS/ConnectJS middleware?Node.js Express app - request objectAngular Http Module considered middleware?Session variables in ExpressJSAdd properties to the req object in expressjs with Typescript