Skip to content
This repository was archived by the owner on Feb 16, 2019. It is now read-only.
This repository was archived by the owner on Feb 16, 2019. It is now read-only.

Internal gRPC connections not working #221

@stevemartinaws

Description

@stevemartinaws

Is this a BUG or FEATURE REQUEST?:

Did you review https://istio.io/help/ and existing issues to identify if this is already solved or being worked on?:

Yes

Bug:
Y

What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details

istioctl version 0.5.1
kubectl version 0.5.1

Is Istio Auth enabled or not ?
No

What happened:
Node gRPC app cannot communicate with go gRPC services internally - this works if using the external NodePort
Worked in 0.0.4

This is the error from the node client process

 { Error: 14 UNAVAILABLE: Connect Failed
    at new createStatusError (/usr/src/app/node_modules/grpc/src/client.js:64:15)
    at /usr/src/app/node_modules/grpc/src/client.js:583:15
  code: 14,
  metadata: Metadata { _internal_repr: {} },
  details: 'Connect Failed' }

I have removed the sidecars from the apps and everything is communicated as expected

What you expected to happen:
We should be able to communicate between services using internal DNS without having to route outside the cluster

How to reproduce it:
run a node gRPCclient calling golang gRPC server, both using sidecar

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions