No KongIngress for Gateway Routes

[shaneutt]

We are not going to support KongIngress with Gateway Routes (e.g. HTTPRoute) as it does not follow the Policy Attachment specification. The purpose of this task is to ensure KongIngress is disabled for these types, and end-users needing the relevant functionality can make requests in the future which should trigger the development of new relevant Policy APIs.

[mflendrich]

This needs to extend to override annotations on dependant resources (e.g. Services) being referenced by *Routes, right?

And we want to be more general and have this change cover all kinds of Gateway API routes, or am I missing something? the description already says that