Oliver Gould
Oliver Gould
@007 I believe that we worked through this issue on slack by disabling external profiles and configuring the override header. Are there any remaining questions or should we close out...
Folding this into #12610
> This also spikes the resources (and caused OOMKill) all of the linkerd-destination pods in cluster A @Sierra1011 Do you know which container in the pod is being OOMKilled? `kubectl...
@Sierra1011 This sounds somewhat similar to another report we had recently that we believe is fixed by https://github.com/linkerd/linkerd2/pull/12598. Updating to the latest edge release should resolve that class of issue....
> The pod being killed was the linkerd-destination pod, and unfortunately I don't have metrics from this any more. There are multiple containers in the destination pod... It sounds like...
> On cluster A, scale a linkerd-injected deployment... This should cause a spike in resources of the Linkerd control plane in cluster B, especially linkerd-destination pods. Thinking about this more,...
This version deprecates the Dial API in favor of the NewClient API.
I want to hold merging this until we've done a release with the existing deps.
> The policy controller fails when it tries to watch some k8s resources (I think all of them). Are you basing this only off of the INFO log messages, or...
`Connection reset by peer (os error 104)` indicates that the API server is tearing down the connection. We can expect this to happen periodically and the client should seamlessly reestablish...