KCNA ยท Kubernetes networking
Ingress, Ingress controllers and Gateway API
Ingress resource vs controller, host/path routing, TLS termination, Gateway API at a conceptual level.
Key points
- An Ingress resource declares HTTP(S) routing rules (host and path to Service, plus TLS termination), but it does nothing until an Ingress controller is running to act on it; ingressClassName picks the controller.
- Gateway API is the newer, role-oriented model (GatewayClass, Gateway, HTTPRoute) delivered as CRDs, and the Kubernetes project recommends it for new work.
Source: https://kubernetes.io/docs/concepts/services-networking/ingress/
Practice questions
What must exist in the cluster for an Ingress resource to actually route traffic?
- An Ingress controller
- A NetworkPolicy for the Ingress
- A headless Service for every host
- A second kube-proxy in IPVS mode
Show answer
Answer: A. An Ingress controller
The Ingress object is only configuration; an Ingress controller (for example one based on NGINX or Envoy) implements it. Nothing in the control plane does this by default.
Which are resource kinds defined by Gateway API?
- GatewayClass
- HTTPRoute
- IngressClass
- NodePortRule
- ServiceMesh
Show answer
Answer: A. GatewayClass, B. HTTPRoute
GatewayClass, Gateway and HTTPRoute are core Gateway API kinds. IngressClass belongs to the Ingress API, and Endpoints/NodePortRule are not Gateway API resources.
True or false: Creating an Ingress object is enough for Kubernetes to start routing HTTP traffic, because the API server handles it.
Show answer
Answer: False
False. The API server only stores the object; a separately installed Ingress controller reads it and configures a proxy or load balancer.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
