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.

Sign up for GitHub

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

Jump to bottom

kuma-cp: fix an issue with Access Log Server on Kubernetes by replacing Google gRPC client with Envoy gRPC client #306

Merged

yskopets merged 1 commit into master from fix/grpc-access-log-server-on-k8s

Oct 2, 2019

Contributor

yskopets commented Oct 2, 2019 •

edited

Notes

Notice that the actual cause of the issue was unrelated to Google gRPC vs Envoy gRPC
Instead, it was a naming issue:
- kuma-dp was listening on a Unix socket A
- while kuma-cp was configuring Envoy to use Unix socket B

yskopets requested a review from jakubdyszkiewicz

October 2, 2019 14:05

yskopets added kuma-cp labels

yskopets added this to the 0.2.0 milestone


          kuma-cp: fix an issue with Access Log Server on Kubernetes by replaci…

38f335e

…ng Google gRPC client with Envoy gRPC client

yskopets force-pushed the fix/grpc-access-log-server-on-k8s branch from 64be3ac to 38f335e Compare

October 2, 2019 14:09

yskopets merged commit f7ff4f7 into master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment