Roadmap for promoting Gateway API Extension CRDs from v1alpha1 to GA #9474
Unanswered
justin-wei-visma
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Envoy Gateway team,
We are currently evaluating Envoy Gateway as a replacement for our existing Ingress NGINX setup.
Several features we require depend on the Envoy Gateway extension CRDs, especially:
SecurityPolicyClientTrafficPolicyBackendTrafficPolicyAccording to the current API reference, these resources are still provided under
gateway.envoyproxy.io/v1alpha1.Could you please clarify:
v1alpha1to a stable/GA API version?v1alpha1APIs?We are considering Envoy Gateway for production use, so understanding the API stability and migration plan is important for our decision.
Thank you!
All reactions