-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Flomesh Service Mesh as a downstream implementation #1421
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -12,6 +12,7 @@ Implementors and integrators of Gateway API are encouraged to update this docume | |||||
- [Cilium][16] (work in progress) | ||||||
- [Contour][3] (alpha) | ||||||
- [Emissary-Ingress (Ambassador API Gateway)][4] (alpha) | ||||||
- [Flomesh Service Mesh][17] (work in progress) | ||||||
- [Gloo Edge 2.0][5] (work in progress) | ||||||
- [Google Kubernetes Engine][6] (public preview) | ||||||
- [HAProxy Ingress][7] (alpha) | ||||||
|
@@ -42,6 +43,7 @@ Implementors and integrators of Gateway API are encouraged to update this docume | |||||
[14]:#flagger | ||||||
[15]:#cert-manager | ||||||
[16]:#cilium | ||||||
[17]:#flomesh-service-mesh-fsm | ||||||
|
||||||
## Implementations | ||||||
|
||||||
|
@@ -117,6 +119,15 @@ See [here][emissary-gateway-api] for more details on using the Gateway API with | |||||
[envoy]:https://envoyproxy.io | ||||||
[emissary-gateway-api]:https://www.getambassador.io/docs/edge-stack/latest/topics/using/gateway-api/ | ||||||
|
||||||
### Flomesh Service Mesh (FSM) | ||||||
|
||||||
[Flomesh Service Mesh][fsm] is a community driven Kubernetes North-South traffic manager, and provides an implementation of Ingress controller, Gateway API, Load Balancer, and cross-cluster service registration and service discovery. | ||||||
|
||||||
The [Flomesh.io](flomesh) team is actively working towards an implementation of the Gateway API. | ||||||
|
||||||
[fsm]:https://github.com/flomesh-io/fsm | ||||||
[flomesh]:https://fomesh.io | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the catch and apologies on making that typo. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar comment as above, it's possible that your change just never got pushed up. |
||||||
|
||||||
### Gloo Edge | ||||||
|
||||||
Gloo Edge 2.0 is an Istio-native, fully-featured Envoy based API gateway that brings [Gloo Edge][glooedge] functionality to Istio. The [Solo.io][solo] team is actively working towards an implementation of the Gateway API. | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any links where we can track your progress towards Gateway API support? Even a GitHub issue or project would help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have previously created flomesh-io/fsm#18 to track the implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Do you mind linking to that in your description, something like "You can track progress of this implementation here"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @robscott . I've updated PR description accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @naqvis, you may have missed pushing your latest update, I still don't see a link to the tracking issue for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @robscott, I have updated the document and pushed commit#810ca6c. Previously I only made updates to the description of this PR.