v1.4.0 Release-Cycle: Standard Features

[shaneutt]

Note: This discussion is now locked, as scoping for v1.4.0 has concluded.

📣 The release cycle for Release v1.4.0 is starting. We anticipate releasing in time for Kubecon NA in November.

The purpose of this discussion is to do scoping for the Standard channel features for this release.

Note: For Experimental features for this release, see this discussion.

If you have something you want to submit for inclusion in this release, post here using the following template:

# Proposal Name Goes Here

1. Provide a link to the Issue for the proposed feature

2. Do you have sufficient time to lead the development of this feature
     in Gateway API? Do you have anyone else that can help you? (list all)

3. Do you have reviewers ready to support the progress of this feature? (list all)

4. Do you have at least 3 implementations that are ready to support this
        feature by running and reporting on any applicable conformance tests? (list all)

When does scoping end?

As per the scoping documentation we are going to provide ~5 weeks for scoping. This means scoping concludes on Tuesday, May 20th, and at that time this thread will be locked and new features will not be accepted in scope past that point unless there are extenuating circumstances.

Upvoting

Comments on this thread can be upvoted by the community. The amount of upvotes a feature gets will help to inform the overall priority of features in this release. Please upvote as many issues as you like. Please leave an emoji 👍 as well, as this helps us know who voted for what.

Important Links

• Project Board
• Milestone
• Tracking Issue

Important Notes

WARNING: Posting in this thread is exclusively for submissions that meet the above criteria. For instance, this is not a place to suggest inclusion of a feature you're not ready to work on yourself: if you'd like to ask for volunteers for a feature you want, posting on the issue itself as well as using our Slack Channel and Community Meetings are the appropriate places. Off-topic posts will be deleted.

[candita]

BackendTLSPolicy

1. Provide a link to the Issue for the proposed feature

GEP: TLS from Gateway to Backend for ingress (backend TLS termination) #1897

2. Do you have sufficient time to lead the development of this feature in Gateway API? Do you have anyone else that can help you?

Yes, I can lead this. I'm hoping to get more volunteers from my own team and from the community at large.

3. Do you have reviewers ready to support the progress of this feature?

Yes.

4. Do you have at least 3 implementations that are ready to support this feature by running and reporting on any applicable conformance tests?

Yes, there are five known implementations: Contour, Envoy Gateway, NGINX Gateway, Traefik, and Istio.

[mlavacca]

Kong is yet another implementation.

[LiorLieberman]

GatewayClass Supported Features

1. Provide a link to the Issue for the proposed feature: GEP: SupportedFeatures #3164, Change conformance tests to read from supportedFeatures (GEP-2162) #3759, Update Implementer's Guide with SupportedFeatures guidance #2497

2. Do you have sufficient time to lead the development of this feature
   in Gateway API? Do you have anyone else that can help you? (list all)

   Yes, will likely have other folks contribute as well

3. Do you have reviewers ready to support the progress of this feature? (list all)

@robscott @youngnick (both interested in this), myself as well for some parts that wont be implement by myself

4. Do you have at least 3 implementations that are ready to support this
   feature by running and reporting on any applicable conformance tests? (list all)

• envoy-gateway
• cilium
• kong

[youngnick]

I think @mlavacca will have some input to this as well.

[mlavacca]

I think @mlavacca will have some input to this as well.

Yes, I plan to create a memorandum GEP to summarize all the things related to the features lifecycle and the supported features in the GatewayClass object.

[mikemorris]

HTTPRoute Retries

1. GEP: Configurable Retries in HTTPRoute #1731

2. Do you have sufficient time to lead the development of this feature
   in Gateway API? Do you have anyone else that can help you? (list all)

   Yes, and may have help from a member of my team at Microsoft too.

3. Do you have reviewers ready to support the progress of this feature? (list all)

   Seeking reviewers!

4. Do you have at least 3 implementations that are ready to support this
   feature by running and reporting on any applicable conformance tests? (list all)

• gateway api: implement HTTPRoute retries istio/istio#54800
• feat: support GEP-1731 envoyproxy/gateway#5024
• gateway-api: Add support for HTTP Retry cilium/cilium#34720

[shaneutt]

I can be a primary reviewer for the feature.

[guicassolato]

Named route rules

1. GEP: Add Name to HTTPRouteRule and HTTPRouteMatch #995

2. Do you have sufficient time to lead the development of this feature
   in Gateway API? Do you have anyone else that can help you? (list all)
   Yes.

3. Do you have reviewers ready to support the progress of this feature? (list all)
   Not yet.

4. Do you have at least 3 implementations that are ready to support this
   feature by running and reporting on any applicable conformance tests? (list all)

   • Bump gateway API to 1.2.0-rc1 istio/istio#53164
   • Feat: add HTTPRoute-rule name to envoy route metadata envoyproxy/gateway#4561
   • Missing confirmation from a 3rd implementation
     • Not counting Kuadrant, which is interested in this feature but it's not actually an implementation.
     • I believe Avi Kubernetes Operator (AKO) has showed interest in supporting it in the past, but I could not confirm it by looking at the code.

[mikemorris]

I could be a reviewer on this!