Does k8s consul connect work without connect-service-upstreams?

[blake]

Hi @jcampbell,

I just replied on this other thread about dynamic upstreams / transparent proxy redirection.

TLDR; at the moment, Consul requires that services be assigned ports a localhost, but we’re looking to address this in the next release of Consul.

Consul Connect dynamic upstreams

Hi @jcampbell and @parkedwards, You are not misunderstanding the documentation. Currently Consul requires that upstream destinations and ports be manually declared, and it does not support transparent traffic redirection. We’re using the GitHub issue below to track this feature request. The good news is that this feature is on our near term roadmap, and is targeted for Consul 1.10. I hope this helps. Let me know if you have any other questions.