Day 34 : Working with Services in Kubernetes

What are Services in K8s

In Kubernetes, Services are objects that provide stable network identities to Pods and abstract away the details of Pod IP addresses. Services allow Pods to receive traffic from other Pods, Services, and external clients.

Types of Services in Kubernetes

Cluster Ip

Exposes the Service on a cluster-internal IP. Choosing this value makes the Service only reachable from within the cluster. This is the default that is used if you don't explicitly specify a type for a Service. You can expose the Service to the public internet using an Ingress or a Gateway.

Node Port

Exposes the Service on each Node's IP at a static port (the NodePort). To make the node port available, Kubernetes sets up a cluster IP address, the same as if you had requested a Service of type: ClusterIP.

Load Balancer

Exposes the Service externally using an external load balancer. Kubernetes does not directly offer a load balancing component; you must provide one, or you can integrate your Kubernetes cluster with a cloud provider.

External Name

Maps the Service to the contents of the externalName field (for example, to the hostname api.foo.bar.example). The mapping configures your cluster's DNS server to return a CNAME record with that external hostname value. No proxying of any kind is set up.

Task-1:

• Create a Service for your todo-app Deployment from Day-32

• Create a Service definition for your todo-app Deployment in a YAML file.

• Apply the Service definition to your K8s (minikube) cluster using the kubectl apply -f service.yml -n <namespace-name> command.

• Verify that the Service is working by accessing the todo-app using the Service's IP and Port in your Namespace.

Task-2:

• Create a Cluster IP Service for accessing the todo-app from within the cluster

• Create a ClusterIP Service definition for your todo-app Deployment in a YAML file.

• Apply the ClusterIP Service definition to your K8s (minikube) cluster using the kubectl apply -f cluster-ip-service.yml -n <namespace-name> command.

• Verify that the Cluster IP Service is working by accessing the todo-app from another Pod in the cluster in your Namespace.

Task-3:

• Create a LoadBalancer Service for accessing the todo-app from outside the cluster

• Create a LoadBalancer Service definition for your todo-app Deployment in a YAML file.

• Apply the LoadBalancer Service definition to your K8s (minikube) cluster using the kubectl apply -f load-balancer-service.yml -n <namespace-name> command.

• Verify that the Load Balancer Service is working by accessing the todo-app from outside the cluster in your Namespace.