gateway-api icon indicating copy to clipboard operation
gateway-api copied to clipboard

GEP: Mesh Service Binding

Open keithmattix opened this issue 3 years ago • 9 comments

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

keithmattix avatar Aug 04 '22 01:08 keithmattix

/kind gep /area mesh

keithmattix avatar Aug 04 '22 01:08 keithmattix

I've drafted a Google doc for more fluid discussion of this GEP

keithmattix avatar Aug 09 '22 16:08 keithmattix

It would appear the permissions on this google doc are restrictive.

shaneutt avatar Aug 09 '22 19:08 shaneutt

Apologies, the doc should be accessible now!

keithmattix avatar Aug 09 '22 20:08 keithmattix

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

k8s-triage-robot avatar Jan 26 '24 19:01 k8s-triage-robot

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

shaneutt avatar Jan 26 '24 20:01 shaneutt

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

k8s-triage-robot avatar Apr 25 '24 21:04 k8s-triage-robot

I think this will be complete with the release of v1.1

keithmattix avatar Apr 25 '24 21:04 keithmattix