Forward IP range to Kubernetes node running in Vagrant/VirtualBox










1














I have a 3-node Kubernetes cluster setup with Vagrant/Virtualbox. I am setting up a 4th VM that is not attached to the cluster.



I want to configure my 4th node so that it routes all traffic in the Service IP CIDR to a node on the Kubernetes cluster. The specific node doesn't matter since once traffic hits a node it will route to the correct pod as I expect.



For example, let's say I deploy a Rabbit broker on my k8s cluster behind a Service with IP 10.0.0.5 and my cluster service CIDR is 10.0.0.0/24. On my 4th VM, I set up a python script to publish messages to 10.0.0.5. However, 10.0.0.5 is virtual since it is a Service ClusterIP and therefore doesn't know how to route. I want to add a routing rule to automatically send 10.0.0.0/24 traffic to any of the 3 nodes in my cluster.



Can anyone help me out?










share|improve this question




























    1














    I have a 3-node Kubernetes cluster setup with Vagrant/Virtualbox. I am setting up a 4th VM that is not attached to the cluster.



    I want to configure my 4th node so that it routes all traffic in the Service IP CIDR to a node on the Kubernetes cluster. The specific node doesn't matter since once traffic hits a node it will route to the correct pod as I expect.



    For example, let's say I deploy a Rabbit broker on my k8s cluster behind a Service with IP 10.0.0.5 and my cluster service CIDR is 10.0.0.0/24. On my 4th VM, I set up a python script to publish messages to 10.0.0.5. However, 10.0.0.5 is virtual since it is a Service ClusterIP and therefore doesn't know how to route. I want to add a routing rule to automatically send 10.0.0.0/24 traffic to any of the 3 nodes in my cluster.



    Can anyone help me out?










    share|improve this question


























      1












      1








      1







      I have a 3-node Kubernetes cluster setup with Vagrant/Virtualbox. I am setting up a 4th VM that is not attached to the cluster.



      I want to configure my 4th node so that it routes all traffic in the Service IP CIDR to a node on the Kubernetes cluster. The specific node doesn't matter since once traffic hits a node it will route to the correct pod as I expect.



      For example, let's say I deploy a Rabbit broker on my k8s cluster behind a Service with IP 10.0.0.5 and my cluster service CIDR is 10.0.0.0/24. On my 4th VM, I set up a python script to publish messages to 10.0.0.5. However, 10.0.0.5 is virtual since it is a Service ClusterIP and therefore doesn't know how to route. I want to add a routing rule to automatically send 10.0.0.0/24 traffic to any of the 3 nodes in my cluster.



      Can anyone help me out?










      share|improve this question















      I have a 3-node Kubernetes cluster setup with Vagrant/Virtualbox. I am setting up a 4th VM that is not attached to the cluster.



      I want to configure my 4th node so that it routes all traffic in the Service IP CIDR to a node on the Kubernetes cluster. The specific node doesn't matter since once traffic hits a node it will route to the correct pod as I expect.



      For example, let's say I deploy a Rabbit broker on my k8s cluster behind a Service with IP 10.0.0.5 and my cluster service CIDR is 10.0.0.0/24. On my 4th VM, I set up a python script to publish messages to 10.0.0.5. However, 10.0.0.5 is virtual since it is a Service ClusterIP and therefore doesn't know how to route. I want to add a routing rule to automatically send 10.0.0.0/24 traffic to any of the 3 nodes in my cluster.



      Can anyone help me out?







      routing kubernetes vagrant virtualbox






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 12 at 20:19









      Rico

      26.1k94864




      26.1k94864










      asked Nov 12 at 20:01









      bfink

      113110




      113110






















          1 Answer
          1






          active

          oldest

          votes


















          1














          Although you might be able to make routing working with route tables and iptables, I would recommend using a NodePort type of service so that you talk to the IP address of your nodes and not a Virtual IP that is only available within the cluster.






          share|improve this answer




















            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%2f53269271%2fforward-ip-range-to-kubernetes-node-running-in-vagrant-virtualbox%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Although you might be able to make routing working with route tables and iptables, I would recommend using a NodePort type of service so that you talk to the IP address of your nodes and not a Virtual IP that is only available within the cluster.






            share|improve this answer

























              1














              Although you might be able to make routing working with route tables and iptables, I would recommend using a NodePort type of service so that you talk to the IP address of your nodes and not a Virtual IP that is only available within the cluster.






              share|improve this answer























                1












                1








                1






                Although you might be able to make routing working with route tables and iptables, I would recommend using a NodePort type of service so that you talk to the IP address of your nodes and not a Virtual IP that is only available within the cluster.






                share|improve this answer












                Although you might be able to make routing working with route tables and iptables, I would recommend using a NodePort type of service so that you talk to the IP address of your nodes and not a Virtual IP that is only available within the cluster.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 12 at 20:22









                Rico

                26.1k94864




                26.1k94864



























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f53269271%2fforward-ip-range-to-kubernetes-node-running-in-vagrant-virtualbox%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

                    Top Tejano songwriter Luis Silva dead of heart attack at 64

                    政党

                    天津地下鉄3号線