Add gateway api CRDs to kuberentes in-tree APIs

[dudicoco]

What would you like to be added:

Hi, currently the gateway api CRDs need to be installed out-of-tree, they are not included as part of the default kubernetes APIs.

Since the goal of the project is to replace the ingress API it would make sense to include the APIs as part of the stock kubernetes APIs.

Why this is needed:

Make for a more seamless experience for anyone who wants to use the gateway api, reduce the overheads involved in installing CRDs.
By searching the issues in this repo I see that there were requests by users for installing CRDs via helm or kubernetes jobs, including the APIs in-tree would solve these issues.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[youngnick]

The Kubernetes project is actually working to remove things from the k/k repo as much as possible, and is expecting more changes to be delivered like Gateway API.

What we are going back and looking at is a Job to help with installing the CRDs, that implementations will be able to safely include in their Helm charts, that will ensure that at least a compatible version is installed in the cluster when the implementation is.

Please keep an eye on #2678 for that effort.

I'll close this one though, thanks for logging it.

/close

[k8s-ci-robot]

@youngnick: Closing this issue.

In response to this:

The Kubernetes project is actually working to remove things from the k/k repo as much as possible, and is expecting more changes to be delivered like Gateway API.

What we are going back and looking at is a Job to help with installing the CRDs, that implementations will be able to safely include in their Helm charts, that will ensure that at least a compatible version is installed in the cluster when the implementation is.

Please keep an eye on #2678 for that effort.

I'll close this one though, thanks for logging it.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.