Kubernetes API server not accessible from external through IP address












0















on the node that api server is running, when I call curl localhost:8080/api, I see following



{
"kind": "APIVersions",
"versions": [
"v1"
],
"serverAddressByClientCIDRs": [
{
"clientCIDR": "0.0.0.0/0",
"serverAddress": "192.168.152.201:6443"
}
]
}


However, if I do curl 192.168.152.201:6443/api on same machine, I do not get anything back.



Can anyone explain why this is the case and how I can access api server externally?










share|improve this question





























    0















    on the node that api server is running, when I call curl localhost:8080/api, I see following



    {
    "kind": "APIVersions",
    "versions": [
    "v1"
    ],
    "serverAddressByClientCIDRs": [
    {
    "clientCIDR": "0.0.0.0/0",
    "serverAddress": "192.168.152.201:6443"
    }
    ]
    }


    However, if I do curl 192.168.152.201:6443/api on same machine, I do not get anything back.



    Can anyone explain why this is the case and how I can access api server externally?










    share|improve this question



























      0












      0








      0








      on the node that api server is running, when I call curl localhost:8080/api, I see following



      {
      "kind": "APIVersions",
      "versions": [
      "v1"
      ],
      "serverAddressByClientCIDRs": [
      {
      "clientCIDR": "0.0.0.0/0",
      "serverAddress": "192.168.152.201:6443"
      }
      ]
      }


      However, if I do curl 192.168.152.201:6443/api on same machine, I do not get anything back.



      Can anyone explain why this is the case and how I can access api server externally?










      share|improve this question
















      on the node that api server is running, when I call curl localhost:8080/api, I see following



      {
      "kind": "APIVersions",
      "versions": [
      "v1"
      ],
      "serverAddressByClientCIDRs": [
      {
      "clientCIDR": "0.0.0.0/0",
      "serverAddress": "192.168.152.201:6443"
      }
      ]
      }


      However, if I do curl 192.168.152.201:6443/api on same machine, I do not get anything back.



      Can anyone explain why this is the case and how I can access api server externally?







      kubernetes






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 0:28









      Rico

      28.3k94966




      28.3k94966










      asked Nov 15 '18 at 0:23









      Brandon LeeBrandon Lee

      626




      626
























          1 Answer
          1






          active

          oldest

          votes


















          1














          It's related to routing and when you make a call 192.168.152.201 where your traffic is going to.



          Could be one or multiple things, some things to check:




          • Does one of your physical interfaces have 192.168.152.201 configured as its IP address? (ie, ensX, or ethX)


          • What is your default route? What do you get if you type ip route (Linux)


          • If 192.168.152.201 is not one of your physical interfaces, is it an outside service. How do you get from your default route to that?


          • If 192.168.152.201 is, in fact, one of your physical interfaces, do you have any iptables (firewall rules) preventing access to 192.168.152.201:6443 and not 127.0.0.1:6443







          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%2f53310757%2fkubernetes-api-server-not-accessible-from-external-through-ip-address%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














            It's related to routing and when you make a call 192.168.152.201 where your traffic is going to.



            Could be one or multiple things, some things to check:




            • Does one of your physical interfaces have 192.168.152.201 configured as its IP address? (ie, ensX, or ethX)


            • What is your default route? What do you get if you type ip route (Linux)


            • If 192.168.152.201 is not one of your physical interfaces, is it an outside service. How do you get from your default route to that?


            • If 192.168.152.201 is, in fact, one of your physical interfaces, do you have any iptables (firewall rules) preventing access to 192.168.152.201:6443 and not 127.0.0.1:6443







            share|improve this answer




























              1














              It's related to routing and when you make a call 192.168.152.201 where your traffic is going to.



              Could be one or multiple things, some things to check:




              • Does one of your physical interfaces have 192.168.152.201 configured as its IP address? (ie, ensX, or ethX)


              • What is your default route? What do you get if you type ip route (Linux)


              • If 192.168.152.201 is not one of your physical interfaces, is it an outside service. How do you get from your default route to that?


              • If 192.168.152.201 is, in fact, one of your physical interfaces, do you have any iptables (firewall rules) preventing access to 192.168.152.201:6443 and not 127.0.0.1:6443







              share|improve this answer


























                1












                1








                1







                It's related to routing and when you make a call 192.168.152.201 where your traffic is going to.



                Could be one or multiple things, some things to check:




                • Does one of your physical interfaces have 192.168.152.201 configured as its IP address? (ie, ensX, or ethX)


                • What is your default route? What do you get if you type ip route (Linux)


                • If 192.168.152.201 is not one of your physical interfaces, is it an outside service. How do you get from your default route to that?


                • If 192.168.152.201 is, in fact, one of your physical interfaces, do you have any iptables (firewall rules) preventing access to 192.168.152.201:6443 and not 127.0.0.1:6443







                share|improve this answer













                It's related to routing and when you make a call 192.168.152.201 where your traffic is going to.



                Could be one or multiple things, some things to check:




                • Does one of your physical interfaces have 192.168.152.201 configured as its IP address? (ie, ensX, or ethX)


                • What is your default route? What do you get if you type ip route (Linux)


                • If 192.168.152.201 is not one of your physical interfaces, is it an outside service. How do you get from your default route to that?


                • If 192.168.152.201 is, in fact, one of your physical interfaces, do you have any iptables (firewall rules) preventing access to 192.168.152.201:6443 and not 127.0.0.1:6443








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 15 '18 at 0:35









                RicoRico

                28.3k94966




                28.3k94966
































                    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%2f53310757%2fkubernetes-api-server-not-accessible-from-external-through-ip-address%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

                    List item for chat from Array inside array React Native

                    Thiostrepton

                    Caerphilly