Not able to install router via helm chart to connect to ziti controller at port 443 but able to connect via router script

Ziti Overlay
17

Sadath's issue here was that there were no reachable edge listeners ({edge.advertisedHost}:{edge.advertisedPort}) from the client's perspective.

I'm still working to clarify and reproduce @bazooka720 and @yemaney's issues.

{"file":"github.com/openziti/ziti/router/router.go:346","func":"github.com/openziti/ziti/router.(*Router).showOptions","level":"info","msg":"ctrl = {\"OutQueueSize\":4,\"MaxQueuedConnects\":1,\"MaxOutstandingConnects\":16,\"ConnectTimeout\":5000000000,\"DelayRxStart\":false,\"WriteTimeout\":0}","time":"2024-07-18T02:57:31.726Z"}

@yemaney Your last router log showed a ctrl connection error info message. That means the router failed to connect to the controller's {ctrlPlane.advertisedHost}:{ctrlPlane.advertisedPort}. That's an mTLS connection, so if you're advertising port 443/tcp through a load balancer, then ensure it's configured for passthrough TLS (a layer 4 TCP transport proxy, optionally selecting upstream/origin by SNI).

Now I see it's an INFO message, not an ERROR, so I don't think it's a connectivity problem from router to ctrl.