Closed keithmattix closed 1 day ago
/kind gep /area mesh
I've drafted a Google doc for more fluid discussion of this GEP
It would appear the permissions on this google doc are restrictive.
Apologies, the doc should be accessible now!
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Based on recent conversations where we are trying to harden Service
binding as the main way to do Gateway API for Mesh, this is still an ongoing effort and is not stale.
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I think this will be complete with the release of v1.1
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
This is basically finished, but the GEP in the GEP list is listed as GEP-1426, not GEP-1294. We should really fix that, then this can be closed. See https://gateway-api.sigs.k8s.io/geps/gep-1426/ for the details. (May need a redirect from https://gateway-api.sigs.k8s.io/geps/gep-1426/ to gep-1294 once the change is made as well).
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
This last item was fixed by #3359. Closing.
/close
@youngnick: Closing this issue.
What would you like to be added: As the GAMMA initiative seeks to create a model for service mesh implementations within Gateway API, it is necessary to have a mechanism for binding routes to services
This GEP covers the work to design and implement this mechanism..
Why this is needed:
As @shaneutt originally suggested, the first step will be implementing a provisional GEP that sets out the terms of what we're doing - the "What" and "Why" of the solution, and then once we're on the same page, we'll talk more about the "How".
Why this is needed: Without a way to bind routes to services, no further work can continue