In the Kubernetes cluster, Ingress provides an externally accessible URL for the Service and routes access traffic to the backend Service. Which of the following statements about Ingress is correct?

Question

Options

• ABecause Ingress can expose ports or protocols, it is more convenient to access than Service and
• BIf you need to use the Ingress function, you must first install the Ingress Controller on the
• CYou can set an external domain name in the Service, and then access the Ingress through the
• DIngress is a containerized object that manages external access to services in the cluster. The

• A
  17% (8)
• B
  73% (35)
• C
  4% (2)
• D
  6% (3)

Explanation

Option B is correct because an Ingress resource is purely a configuration object - it defines routing rules but has no built-in mechanism to enforce them. An Ingress Controller (such as NGINX, Traefik, or HAProxy) must be deployed separately in the cluster to watch for Ingress resources and actually handle the incoming traffic; without it, the Ingress rules have no effect.

Option A is wrong because Ingress does not expose arbitrary ports or protocols - it only handles HTTP and HTTPS (ports 80 and 443). For other ports or protocols, you still need a NodePort or LoadBalancer Service, making Ingress more limited in scope, not more convenient across the board.

Option C reverses the relationship: domain name routing rules are defined inside the Ingress resource itself, not in the Service. Services have no field for setting external domain names that feed into Ingress.

Option D is wrong because Ingress is not a "containerized object" - it is a Kubernetes API resource (a declarative configuration). The Ingress Controller runs as containers, but the Ingress object itself is just a routing rule definition stored in the Kubernetes API.

Memory tip: Ingress = rulebook, Ingress Controller = the enforcer. You can write all the rules you want, but without the enforcer installed first, nothing gets routed.

No community discussion yet for this question.