Migration to the Kubernetes Gateway API

I am working on a greenfield rollout of Istio, whose first use case is to provide a gateway ingress for external production traffic. Later on we may use Istio for a service mesh as well.

I have become aware of a Kubernetes Gateway API project, to which Istio is contributing. I am aware that the gateway spec and the Istio implementation are unstable at this point. My question is, if there is a good chance that we might want to switch over to using the Kubernetes Gateway API spec at some point, would it be advisable to do that now, before the gateway ingress is live in production, or would it be better to wait until the spec and the Istio implementation are more stable? Iā€™m hoping more for gut reactions than an ironclad recommendation.

1 Like