-
Notifications
You must be signed in to change notification settings - Fork 22
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
gke_ingress_lb_envoy example doen't work #5
Comments
Thanks for reporting this....you're correct..for some reason the envoy sample doesn't register as a valid backend anymore. I'm not sure what could be causing this as it've verified it workes locally w/ the http client can access the healthcheck and grpc server works as normal. the only thing the NEG should check for 'liveness' is the healcheck backend. i'll continue to look ( it was working :( ) |
ok, i needed to add in alpn_protocols tls_context:
common_tls_context:
alpn_protocols: h2
tls_certificates:
- certificate_chain:
filename: "/data/certs/tls.crt"
private_key:
filename: "/data/certs/tls.key" without it the NEG healthehecks was failing (again, this must be a new requirement for GCE NEG healthchecks) anyway, if you wanted to set up the grpc client,server and envoy on your laptop , here's some inf get the envoy binary
Run envoynow that you have envoy outside, run the config (you'll need to edit the certs path)
Run GRPC service
Run clients
|
I tested
gke_ingress_lb_mux
example and it did work. Butgke_ingress_lb_envoy
did not work on same environment. (and i didn't change any codes)For details,
kubectl describe
,kubectl logs
)To fix this problem I try to change port, add initialDelay on health-check, but none of these worked.
The text was updated successfully, but these errors were encountered: