Skip to content

Latest commit

 

History

History
14 lines (8 loc) · 840 Bytes

03-20-connection-refused.md

File metadata and controls

14 lines (8 loc) · 840 Bytes

Connection Refused Errors

Symptom

You get either the Connection reset by peer response or the GOAWAY response when you attempt to establish the connection between a service without a sidecar and a service with a sidecar.

Cause

By default, mutual TLS (mTLS) is enabled in the service mesh. As a result, every element of the service mesh must have an Istio sidecar with a valid TLS certificate to allow communication.

Remedy

  • To whitelist a service without a sidecar and disable mTLS traffic for it, create a DestinationRule.
  • To allow connections between a service without a sidecar and a service with a sidecar, create a Peer Authentication in the PERMISSIVE mode.