Add support for new Gateway infrastructure labels, possibly deprecate GatewayClassConfig copyAnnotations

[mikemorris]

Is your feature request related to a problem? Please describe.

The GatewayClassConfig copyAnnotations field currently enables similar functionality (and was a necessary workaround prior to this functionality landing upstream), but is a bit awkward UX for this configuration as populating these values requires both configuring annotations on the Gateway resources itself and then setting a global configuration from a resource referenced by the GatewayClass to select specific annotation keys to be copied, which is several steps removed from the resource a user will want to configure (the underlying Service provisioned by a user-configured Gateway resource) - this can be a source of confusion.

Feature Description

Add support for the new infrastructure field as described in https://kubernetes.io/blog/2023/11/28/gateway-api-ga/#gateway-infrastructure-labels, which allows a user to specify labels and annotations on a Gateway resource which should be populated through to any underlying resources provisioned by the Gateway API controller implementation.

Use Case(s)

This will enable a more direct UX for configuring labels and annotations for the underlying load balancer Service resources provisioned by Gateways for use cases such as customizing cloud load balancer types or timeouts as described in the linked Discuss post.

References

• https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayInfrastructure
• GEP-1762: In Cluster Gateway Deployments
  • Details on required labels and suggested naming conventions for generated Service and Deployment resources and using the infrastructure field to configure labels and annotations on underlying resources.
• GEP-1867: Per-Gateway Infrastructure
  • Introduced the infrastructure field with a per-gateway parametersRef

[sophie-gairo]

Hey Mike! We just had a good preliminary discussion around options for this, we'll circle back here when we have some more info, thanks :D