heroku-buildpack-envoy-proxy's Introduction

envoy-buildpack-envoy-proxy

This is currently a proof of concept on using envoy proxy as a heroku router.

requirements

a private space app with spaces-router-bypass enabled.
APP_ID configured to point to the app's UUID. This may change in the future to not require it.

setup using go-getting-started

heroku apps:create --space some-space -a some-app
heroku buildpacks:add https://github.com/heroku/heroku-buildpack-envoy-proxy
heroku buildpacks:add heroku/go
heroku sudo labs:enable spaces-router-bypass

cd path/to/go-getting-started
git push [email protected]:some-app.git master

current supported heroku features

ACM - integrates such that you can heroku certs:auto:enable your app and still get the cert working with the envoy proxy.
http availability - responds to probes to the availability prober.

future roadmap

tracing
metrics
logs

heroku-buildpack-envoy-proxy's People

Contributors

Stargazers

Watchers

heroku-buildpack-envoy-proxy's Issues

How to use envoy proxy in heroku app?

I created a web-app (static HTML + JS) served with Nginx, which uses grpc-web to call grpc service through envoy proxy.

I then created a docker-compose.yml with Nginx + Envoy + gPRC server that runs successfully at local. And I want to deploy all three components as one Heroku app together using heroku.yml.

It looks like the envoy proxy, which should be exposed at port 9000 is not available. The error message received is:

Failed to load resource: net::ERR_TIMED_OUT, https://yg-grpc.herokuapp.com:9090/torch.Predictor/GetPredict

The Heroku App in test is available at:
https://yg-grpc.herokuapp.com/#/projects/cv/image

Please let me know what information or action is needed for further discussion.

Thank you very much!

Recommend Projects