You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.
I have a Cloudprober custom docker image with the this tool
So i can perform this: command: "/bin/grpc_health_probe -addr=@target@:50051"
But in my clusters, all services serve behind the istio-proxy.
So we have the same problem related here: #438
The @target@ come only with the name of the service like my-app, but to work in Istio we need the FQDN of the service like my-app.my-namespace.svc.cluster.local.
See the error:
I0828 14:48:16.646542 1 external.go:510] Running external command: /bin/grpc_health_probe -addr=my-app:50051
E0828 14:48:17.653696 1 external.go:519] external probe process died with the status: exit status 2. Stderr: timeout: failed to connect service "my-app:50051" within 1s
There some way to deal with this?
The text was updated successfully, but these errors were encountered:
I guess we can provide a way to access target labels on the command line the same way as @target@, for example @target.label.fqdn@. I'll take a stab at it
#454 adds the way to access target's fqdn using "@target.label.fqdn@" in command arguments. Can you please give that a try and let me know if it's not working.
#454 adds the way to access target's fqdn using "@target.label.fqdn@" in command arguments. Can you please give that a try and let me know if it's not working.
This work perfectly, thank you again for the fast resolution 👍
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have config an external probe to can perform probes in gRPC service.
I have a Cloudprober custom docker image with the this tool
So i can perform this:
command: "/bin/grpc_health_probe -addr=@target@:50051"
But in my clusters, all services serve behind the istio-proxy.
So we have the same problem related here: #438
The
@target@
come only with the name of the service likemy-app
, but to work in Istio we need the FQDN of the service likemy-app.my-namespace.svc.cluster.local
.See the error:
There some way to deal with this?
The text was updated successfully, but these errors were encountered: