Upstream connect error or disconnect/reset before headers. reset reason: connection termination

Hi,

I have Kong-Ingress controller on my managed kubernetes cluster and everything is working fine. I have istio inject enable = true for side car stuff life tracing

And when i activate the plugin zipkin pointing to the istio-system zipkin server i get this error:

upstream connect error or disconnect/reset before headers. reset reason: connection termination

Plugin:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
name: zipkin
labels:
global: “true”
config:
http_endpoint: http://zipkin.istio-system:9411/api/v2/spans
sample_ratio: 1.0
plugin: zipkin

Any idea?

Since this traffic goes via Istio’s envoy, make sure that the host header is correctly set and the side-car envoy can resolve where to send the request to inside the mesh.

Sorry, i can not understand your comment.

Just activating the plugin the system doesn´t work. The plugin zipking is pointing to the zipkin istio namespace:port.
The host header is from who?

Do you have any sample?

I don’t have a sample or an Istio cluster with me right now to debug this.

You might want to try to instead use zipkin.istio-system.svc as the service name in http endpoint.

still doesn´t work with http endpoint.

Try it with:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
name: zipkin
labels:
global: “true”
config:
http_endpoint: http://zipkin.istio-system:9411/api/v2/spans
sample_ratio: 1
enabled: true
plugin: zipkin

I belive that could be istio configuration that is not enable for collector zipkin port

At this moment it´s working without kong plugin, only with istio side car injector on kong-ingress-controller


© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ