In terms of core abstractions provided by Kubernetes for service networking, how many types of services are primarily defined?

In terms of core abstractions provided by Kubernetes for service networking, how many types of services are primarily defined?

• A. Two
• B. Three
• C. Five
• D. Four

Answer: (D)

Kubernetes provides four service types for networking. These are ClusterIP, NodePort, LoadBalancer, and ExternalName. ClusterIP assigns an internal IP so the service is reachable only within the cluster, which is the default behavior. NodePort opens a static port on every node, allowing external access by connecting to any node’s IP and that port. LoadBalancer requests an external load balancer from the cloud provider, giving a single external IP that forwards to the service. ExternalName maps the service to an external DNS name, returning a CNAME to that name rather than routing to pods directly. Note that Ingress is not a Service type; it’s a separate resource used for HTTP(S) routing in front of services.

Kubernetes provides four service types for networking. These are ClusterIP, NodePort, LoadBalancer, and ExternalName. ClusterIP assigns an internal IP so the service is reachable only within the cluster, which is the default behavior. NodePort opens a static port on every node, allowing external access by connecting to any node’s IP and that port. LoadBalancer requests an external load balancer from the cloud provider, giving a single external IP that forwards to the service. ExternalName maps the service to an external DNS name, returning a CNAME to that name rather than routing to pods directly. Note that Ingress is not a Service type; it’s a separate resource used for HTTP(S) routing in front of services.