Kubernetes supports different kinds of service types such as following:
- ClusterIP: The service of type, ClusterIP, can only be exposed to other services running within the same Kubernetes cluster. The default ServiceType is ClusterIP.
123456789101112
kind: Service
apiVersion: v1
metadata:
name: hello-service
spec:
selector:
app: HelloApp
ports:
- protocol: TCP
port: 80
targetPort: 9376
nodePort: 30061
- NodePort: The service of type, NodePort, can be exposed externally at a static port. The service address would look like NodeIP:NodePort. External APIs can invoke the NodePort services.
- LoadBalancer: The service of type, LoadBalancer, can be exposed externally using cloud providers’ load balancer.
12345678910111213141516171819
kind: Service
apiVersion: v1
metadata:
name: hello-service
spec:
selector:
app: HelloApp
ports:
- protocol: TCP
port: 80
targetPort: 9376
nodePort: 30061
clusterIP: 10.0.171.239
loadBalancerIP: 78.11.24.19
type: LoadBalancer
status:
loadBalancer:
ingress:
- ip: 146.148.47.155
- ExternalName: The service of type, ExternalName, is mapped to an external name, such as helloapp.vitalflux.com.
Latest posts by Ajitesh Kumar (see all)
- Retrieval Augmented Generation (RAG) & LLM: Examples - February 15, 2025
- How to Setup MEAN App with LangChain.js - February 9, 2025
- Build AI Chatbots for SAAS Using LLMs, RAG, Multi-Agent Frameworks - February 8, 2025
I found it very helpful. However the differences are not too understandable for me