Graduate ExperimentalGatewayAPISupport feature to beta

[irbekrm]

cert-manager can auto-generate certs for gateway.networking.k8s.io Gateway resources (gateway-shim) and supports solving ACME HTTP-01 challenges using gateway.networking.k8s.io resources. Both these features are gated behind an alpha ExperimentalGatewayAPISupport cert-manager feature. The Gateway API itself has now graduated to beta.
cert-manager currently (v1.10) creates v1alpha2 gateway.networking.k8s.io resources, in v1.11 we should start creating v1beta1 (#5564 ). Both v1alpha2 and v1beta Gateways are watched by gateway-shim due to resource conversion.

Perhaps this is a good time to start thinking about graduating ExperimentalGatewayAPISupport feature to beta.

Some things we might want to do before graduating:

• consider how we'll ensure users installations don't crash after enabling this feature Allow Gateway API feature to be enabled in clusters that don't have GWAPI CRDs installed #5616
• define a feature policy (do we want beta features off by default)? Describe cert-manager feature policy website#1125
• consider whether we will want to support any of the other gateway.networking.k8s.io route types https://gateway-api.sigs.k8s.io/concepts/api-overview/#route-summary-table and if yes, how that might look like
• consider how mature is the ecosystem around Gateway API (the supported gateway controllers https://gateway-api.sigs.k8s.io/implementations/)
• do we need better examples how cert-manager can be used with Gateway API?
• (possibly related to above point) our e2e tests for gateway-shim currently create Gateway CRs that aren't actually picked up by gateway controller- should we have more realistic tests?
• some other small fixes
  • Fail with a clear error message if a Gateway TLS listener has a cross-namespace secret reference #5610

/kind feature

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/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/test-infra repository.