Accessing a Kubernetes service using nodePort from external load balancer

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












When I expose the kubernetes service using nodePort , then I can access the port/service using any workder node IP:PORT , even if the service is just actually running on just one node.



What would be the recommended way of accessing the service from an external load balancer where session persistence is required , should I just dynamically discover the extact node on which the service is running so that the kube proxy can proxy it to local node port , OR accessing the service on all the nodes from the external load balancer will still be OK to do and serve the same purpose?









share

























    up vote
    0
    down vote

    favorite












    When I expose the kubernetes service using nodePort , then I can access the port/service using any workder node IP:PORT , even if the service is just actually running on just one node.



    What would be the recommended way of accessing the service from an external load balancer where session persistence is required , should I just dynamically discover the extact node on which the service is running so that the kube proxy can proxy it to local node port , OR accessing the service on all the nodes from the external load balancer will still be OK to do and serve the same purpose?









    share























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      When I expose the kubernetes service using nodePort , then I can access the port/service using any workder node IP:PORT , even if the service is just actually running on just one node.



      What would be the recommended way of accessing the service from an external load balancer where session persistence is required , should I just dynamically discover the extact node on which the service is running so that the kube proxy can proxy it to local node port , OR accessing the service on all the nodes from the external load balancer will still be OK to do and serve the same purpose?









      share













      When I expose the kubernetes service using nodePort , then I can access the port/service using any workder node IP:PORT , even if the service is just actually running on just one node.



      What would be the recommended way of accessing the service from an external load balancer where session persistence is required , should I just dynamically discover the extact node on which the service is running so that the kube proxy can proxy it to local node port , OR accessing the service on all the nodes from the external load balancer will still be OK to do and serve the same purpose?







      load-balancing kubernetes kube-proxy





      share












      share










      share



      share










      asked 1 min ago









      Ijaz Khan

      3,15531333




      3,15531333

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475311%2faccessing-a-kubernetes-service-using-nodeport-from-external-load-balancer%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475311%2faccessing-a-kubernetes-service-using-nodeport-from-external-load-balancer%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay