smarsh-tim

I found the problem!! The `providerID` that's missing is on the `kind: Node` resource that's on the workload cluster - not the bootstrap cluster. So in this version upgrade something...

I tracked down the issue. I would like to see some additional logging in emissary pod logs when it switches back to HTTP even though it's defined as HTTPS. Ultimately...

I did some further testing today, and now my endpoint is still showing two HTTP listeners created in the logging. However, HTTPS requests are resolving inconsistently. Some times the request...

I think I found a root cause. I have multiple emissary-ingress instances, and two of them had incidentally grabbed the same External IP with kube-vip. Took a while to find...