search

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
https://docs.solo.io/
Apache License 2.0
4.03k stars 433 forks source link

Provide Tooling to Convert Legacy APIs to Gateway API #8897

Open danehans opened 7 months ago

danehans commented 7 months ago

Gloo Edge Product

Enterprise

Gloo Edge Version

Latest

Is your feature request related to a problem? Please describe.

As a Gloo Gateway user, I would like tooling that simplifies transitioning from legacy APIs to Gateway API. Without making this process simple and effective, I may never make the transition.

Describe the solution you'd like

I would like to use the ingress2gateway tool for simplifying the conversion. This tool is extensible, allowing implementations to add native/legacy APIs as conversion sources.

Describe alternatives you've considered

N/A

Additional Context

danehans commented 7 months ago

cc @sam-heilbron @linsun

EItanya commented 7 months ago

@danehans I didn't realize that tool existed, good callout! I began looking through the code and I definitely think it could be worth exploring, but I think we should also consider adding this functionality to glooctl for users who are familiar with that tool and already use it quite a bit.

danehans commented 7 months ago

Can glooctl be extended? If so, that could provide the best of both worlds. The biggest benefit of the ingress2gateway approach is having the community backing to help with bug fixes and features.

github-actions[bot] commented 2 weeks ago

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.