<p>Im using cluster (with master, and nodes with pods), but how can I use the services in nodes too? to expose the internet to node environment (using services) and not the master environment.</p>

<p>my scenario (in test yet) is:</p>

<ul>
<li>Have a master and another node (two environments). My pods is running in my node environment, you can see below (kubectl get pod -o wide):
<a href="https://i.stack.imgur.com/zJKw6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/zJKw6.png" alt="enter image description here"></a> </li>
</ul>

<p>I need expose the service where is the node is, and not the master. Because, if I expose the master, and the master goes down, all the service stop.</p>

TitaoYamamoto
<p>You seem to be inclined towards NodePort Services so I guess you are not using a cloud provider (as with a cloud provider you could use LoadBalancer). </p>

<p>Since you have multiple Nodes you then need to choose which to expose externally and how. You could put <a href="https://medium.com/@maniankara/kubernetes-tcp-load-balancer-service-on-premise-non-cloud-f85c9fd8f43c" rel="nofollow noreferrer">an external Load Balancer in front of the cluster so that load is balanced between nodes</a>. That won't be part of the cluster so would have to be configured separately to know which IPs/nodes to route to. </p>

<p>Or you can consider using a single node for routing. The node would only be sending on traffic using the kube-proxy without going into the app content (L4 not L7) so it can route without a lot of processing, which helps to mitigate the risk of it becoming unavailable. But it would still be only a single node and depending on its hardware there would be a risk it could go down for other reasons. So there are tradeoffs to be made when deciding what setup for exposing externally is best for your cluster - you need to choose whether you want to maintain a load balancer in addition to the cluster and whether it would be more reliable than using a node.</p>
