Hands-On Microservices with Kubernetes

Service types in Kubernetes

Kubernetes services always have a type. It's important to understand when to use each type of service. Let's go over the various service types and the differences between them:

• ClusterIP (default): The ClusterIP type means that the service is only accessible inside the cluster. This is the default, and it's perfect for microservices to communicate with each other. For testing purposes, you can expose such services using kube-proxy or port-forwarding. It is also a good way to view the Kubernetes dashboard or other UIs of internal services, such as Argo CD in Delinkcious.

If you don't specify a type of ClusterIP, set the ClusterIP to None.

• NodePort: A service that's of the NodePort type is exposed to the world ...