Skip to content
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

api: add HTTP endpoint for compiled discovery chain for external integrations #6213

Closed
banks opened this issue Jul 25, 2019 · 0 comments
Closed
Labels
theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies
Milestone

Comments

@banks
Copy link
Member

banks commented Jul 25, 2019

We should probably/maybe have an HTTP version of the “compiled discovery chain” RPC for 1.6.0. So far everything Envoy can do can at least in theory be done by any other proxy or native app via our API. Concrete use-cases even beyond other sidecar proxy parity - integrating Ambassador or other north-south configs with things like routing/splitting config.

We'd need to review the graph/compile output and decide if we are confident enough to expose it as it is though as it becomes harder to mutate once we put it in the API.

@banks banks added this to the 1.6.0-beta3 milestone Jul 25, 2019
@rboyer rboyer modified the milestones: 1.6.0-beta3, 1.6.0-final Jul 26, 2019
@rboyer rboyer added the theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies label Jul 30, 2019
@rboyer rboyer modified the milestones: 1.6.0-final, 1.6.0-rc1 Jul 30, 2019
@rboyer rboyer closed this as completed Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies
Projects
None yet
Development

No branches or pull requests

2 participants