Which Kubernetes service type is NOT considered a standard service type?

Which Kubernetes service type is NOT considered a standard service type?

• A. ClusterIP
• B. NodePort
• C. Ingress
• D. LoadBalancer

Answer: (C)

Exposing applications in Kubernetes uses Service resources that come in a few standard types: ClusterIP for internal access, NodePort to expose on node ports, and LoadBalancer to provision an external load balancer. Ingress is not a Service type; it’s a separate resource that defines HTTP/HTTPS routing rules and relies on an Ingress Controller to implement those rules. With Ingress you can route traffic to multiple backend services behind a single IP using hostnames and paths, which is a different mechanism from a Service type that directly exposes endpoints for one service. So, the option that isn’t a standard service type is Ingress. In practice, you typically have internal Services (often ClusterIP) and an Ingress resource with a controller to provide external access and traffic routing to those services.

Exposing applications in Kubernetes uses Service resources that come in a few standard types: ClusterIP for internal access, NodePort to expose on node ports, and LoadBalancer to provision an external load balancer. Ingress is not a Service type; it’s a separate resource that defines HTTP/HTTPS routing rules and relies on an Ingress Controller to implement those rules. With Ingress you can route traffic to multiple backend services behind a single IP using hostnames and paths, which is a different mechanism from a Service type that directly exposes endpoints for one service. So, the option that isn’t a standard service type is Ingress. In practice, you typically have internal Services (often ClusterIP) and an Ingress resource with a controller to provide external access and traffic routing to those services.