Add support for (all) CRDs in Gateway API

[hbagdi]

This is an umbrella issue to track all the work that needs to be done to support CRDs being worked in the gateway-api sub-project of SIG-Network:

https://github.com/kubernetes-sigs/gateway-api

[hbagdi]

This is currently blocked on #686

[shaneutt]

We're going to provide an initial implementation of Gateway APIs using the recently released v0.2.x specification.

Recent work which attempted to add single controller multi proxy support in DBLESS mode sparked @Kong/team-k8s to do a spike for a new architectural direction for the Kubernetes Ingress Controller (KIC), dubbed "Railgun".

The first Gateway API implementation will be done against the railgun KIC architecture and @Kong/team-k8s will be grooming this issue for further priority in the coming weeks.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[shaneutt]

With several KIC 2.0 releases done (and since that work is a pre-requisite for our Gateway API work) I wanted to do a status update:

After KIC 2.0 Beta is launched we will be putting effort into an initial implementation of Gateway APIs. The new target given recent updates will be to support v0.3.0 however, rather than v0.2.0.

This issue is the follow-up for the basic, minimal implementation to get us started: kubernetes-sigs/gateway-api#708

[shaneutt]

The planning and organization for Gateway API integration has changed significantly since this issue was originally posted, and instead of this issue tracking the progress of development we will be using Github Milestones.

The follow up from here can be seen in our Milestone Overview in the relevant KEP, and you can track the progress of the next milestone from here via the Gateway APIs - Milestone 1

[hbagdi]

@shaneutt This issue is linked from https://gateway-api.sigs.k8s.io/implementations/. Either re-open this issue or update the implementations page. I recommend the former.

[shaneutt]

For anyone who comes here from the gateway implementations doc, just note that we're no longer tracking things via this issue, as stated above we're tracking progress via the KEP:

https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md

And the milestones:

https://github.com/Kong/kubernetes-ingress-controller/milestones

[shaneutt]

At this point this issue is being closed as we're no longer using it for tracking Gateway API support and the link to it from the Gateway API implementations page has been removed in favor of the now present preview documentation in docs.konghq.com.

Tracking (and contributing) planning and design for Gateway API support in KIC can be done via the Gateway API KEP.

Tracking (and contributing) development for HTTPRoute, TCPRoute, UDPRoute, and TLSRoute has moved to our Gateway API Milestone #2 and the individual issues therein.

Tracking support level and maturity for Gateway API can be done using the Feature Gates Documentation.

Also watch our blog posts for upcoming news about Gateway API support, which we kicked off with the 2.2 Release post which introduced Gateway API support as a technical preview in KIC.