MENU
This an Ingress configuration. What is the equivalent Gateway API configuration?
Question 19 source Ingress
A)
Question 19 option A
B)
Question 19 option B
C)
Question 19 option C
D)
Question 19 option D
Option B correctly represents the Ingress as a Gateway and an attached HTTPRoute. The Gateway is named cilium, uses gatewayClassName: cilium, and exposes an HTTP listener on port 80. The HTTPRoute uses parentRefs with the same Gateway name, cilium, so the route attaches to the declared listener. Its two rules preserve the original routing behavior: /details with PathPrefix targets the details Service on port 9080, while / with PathPrefix targets productpage on port 9080.
Option A declares a Gateway named cilium but attaches its route to nginx-gateway. Because the parent reference does not identify the displayed Gateway, it is not equivalent. Options C and D use kind: Route; the correct resource kind for HTTP path routing is HTTPRoute. They also contain malformed or altered backend and matching fields. Option D changes the details backend name, while option C contains incorrect route structure and path content.
Cilium's official migration example uses the same conversion pattern: the Ingress class becomes the Gateway's class, paths move into HTTPRoute.rules, and the route identifies its Gateway through parentRefs.
The supplied key incorrectly identifies A. The verified answer is B.
Official references
HTTP Migration Example.
Study Guide topic: Service Mesh.