Oliver Gould
Oliver Gould
linkerd_reconnect: Failed to connect error=Connection refused (os error 111) after installing 2.11.1
It looks like the policy controller is unable to contact the Kubernetes API. Can you try the latest Linkerd stable-2.11.2 to confirm whether the problem is still present?
linkerd_reconnect: Failed to connect error=Connection refused (os error 111) after installing 2.11.1
> DEBUG ThreadId(01) policy:watch{port=9443}:controller{addr=localhost:8090}:endpoint{addr=127.0.0.1:8090}: linkerd_tls::client: Peer does not support TLS reason=loopback This is innocuous. It's indicating that the proxy shouldn't attempt mTLS to a container in the same pod. ---...
linkerd_reconnect: Failed to connect error=Connection refused (os error 111) after installing 2.11.1
It also sounds like #8296 may help resolve this in some cases
stable-2.12 will include new routing primitives that enable this. This feature is tentatively planned for 2.13.
@cabrinoob the edge release notes typically only cover changes since the prior edge release. we're still working on putting together comprehensive release notes (and docs) for stable-2.12.0. You might refer...
@scirner22 Yes, we're actively working on this for the next major release. Most of the API planned at this point (basically, we're using the Gateway API HTTPRoute types that Linkerd...
> the breaking change was likely https://github.com/linkerd/linkerd2/pull/6887. That doesn't seem likely to me. This change added 443 to the proxy's list of default opaque ports. This should only really impact...
> As far as I understood the controller was made redundant and all components talk directly to the K8s API. No, Linkerd proxies continue to use the controller components for...
I don't think it's in-scope for the failover controller to have a means to run arbitrary code. However, it shouldn't be too hard to write something that does this based...
I recommend trying the most recent Linkerd stable release, 2.11.4. You can also try using the latest proxy-init version, 1.6.2.