aaa: Migrate to Gateway API.

[ameukam]

we currently serve all workloads using the default GKE ingress controller. we should migrate to Gateway API when it reaches 1.0 on the GKE cluster.

Reference:

• https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api

[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

[ameukam]

/remove-lifecycle stale /kind feature /area infra/gcp /lifecycle frozen /priority backlog

[BenTheElder]

Hmm, what's the argument here? The gateway project is great, but we're doing very simple things and migrating has a cost.

[ameukam]

Nothing very specific. Happy to close this if we don't think there is a need to migrate to HTTPRoutes.