Deploying and Managing Services Using Rancher Manager - Part I

At this stage, we have a Deployment running with 3 Pods. However, these Pods are not accessible neither from the outside world nor from other applications within the cluster. To make them so, we need to use Services.

ℹ️ A Service is an abstraction that defines a logical set of Pods and a policy by which to access them. Services enable a loose coupling between dependent Pods.

A Service can be of the following types:

• ClusterIP: Exposes the Service on a cluster-internal IP (only reachable from within the cluster). This is useful when you want to expose a Service to other applications within the cluster.

• NodePort: Exposes the Service on each Node's IP at a static port. If your cluster has 3 nodes, 3 ports will be opened on each node. If you want your service to be accessible from the outside world, your nodes should have public IP addresses.

• LoadBalancer: Exposes a single Deployment on an external load balancer. This is not a built-in feature of Kubernetes and requires a cloud provider that supports the Service type LoadBalancer. The LoadBalancer is a standalone server that sits outside the cluster and forwards traffic to the cluster.