A library consortium is tired of Ingress objects that only work after controller-specific annotations. What is a primary motivation for moving toward Gateway API?
Select an answer to reveal the explanation.
Short Explanation
Classic Ingress often becomes a pile of vendor sticky notes (annotations) that do not travel well. Gateway API pushes more of that routing intent into standard objects so libraries are less locked to one controller’s dialect.
Full Explanation
Many Ingress features historically lived in controller-specific annotations, which hurt portability and clarity. Gateway API addresses those limits by modeling Gateways, listeners, and Routes as first-class API resources with richer, more consistent expressiveness. Controllers still implement the API; the point is a better shared contract than annotation spaghetti.