GEP: Mesh Representation

kubernetes-sigs / gateway-api

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

https://gateway-api.sigs.k8s.io

Apache License 2.0

1.8k stars 468 forks source link

GEP: Mesh Representation #1291

Open keithmattix opened 2 years ago

keithmattix commented 2 years ago

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 representing a mesh (follow link for definition) using the Gateway API.

This GEP covers the work to design and implement this mechanism.

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 represent a mesh using Gateway API, no other work can continue.

keithmattix commented 2 years ago

/kind gep

keithmattix commented 2 years ago

/area mesh

k8s-ci-robot commented 2 years ago

@keithmattix: The label(s) area/mesh cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes-sigs/gateway-api/issues/1291#issuecomment-1203079036): >/area mesh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

keithmattix commented 2 years ago

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

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

youngnick commented 1 year ago

/remove-lifecycle stale

/lifecycle frozen since this will stay until we do a lot more on GAMMA work.