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

[request]: GRPC Healthchecks #76

Closed
smy2748 opened this issue Jun 12, 2019 · 1 comment
Closed

[request]: GRPC Healthchecks #76

smy2748 opened this issue Jun 12, 2019 · 1 comment
Labels
Roadmap: Proposed We are considering this for inclusion in the roadmap.

Comments

@smy2748
Copy link

smy2748 commented Jun 12, 2019

Tell us about your request
My team has been creating a lot of GRPC services recently to cut down on client code creation. We had hoped App Mesh would expose Envoy's grpc healthcheck configuration in some manner so we could use it (https://www.envoyproxy.io/docs/envoy/v1.7.0/api-v2/api/v2/core/health_check.proto#core-healthcheck-grpchealthcheck).

Which integration(s) is this request for?
AppMesh + Fargate

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently we're relying on running a simplistic second service to take http traffic to a specific port and forward the call via grpc to the actual service in order to perform healthchecks. It would be better performance-wise to be able to set up healthchecks that were able to directly call the grpc service.

Are you currently working around this issue?
Side service that accepts http, makes a grpc call, and returns the health that way

Additional context

Attachments

@smy2748 smy2748 added the Roadmap: Proposed We are considering this for inclusion in the roadmap. label Jun 12, 2019
@lavignes
Copy link

Resolving as a duplicate of #96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Roadmap: Proposed We are considering this for inclusion in the roadmap.
Projects
None yet
Development

No branches or pull requests

2 participants