Accessing a Kubernetes service using nodePort from external load balancer
Clash 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?
load-balancing kubernetes kube-proxy
add a comment |Â
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?
load-balancing kubernetes kube-proxy
add a comment |Â
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?
load-balancing kubernetes kube-proxy
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
load-balancing kubernetes kube-proxy
asked 1 min ago
Ijaz Khan
3,15531333
3,15531333
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password