Bridge-To-Kubernetes
Bridge-To-Kubernetes copied to clipboard
Azure
Istio Support
Ive noticed that Bridge to Kubernetes doesn't support Istio service mesh at the moment. In fact, I've seen that you specifically added a check to see if an Istio sidecar is injected into the container and then exit out. Could you explain what the issue with Istio is and why you specifically only check for Istio and no other service mesh? Does that mean other service meshes are supported? And does it not work with Istio at all or only in specific circumstances? Would be great if you can shine some light on this.
As a workaround I'm thinking about duplicating the pod/deployment I'm trying to debug and then use a virtual service to route based on a header. Then I could use bridge to Kubernetes without isolation to redirect all traffic to the duplicated pod/deployment to my local machine. Do you see any issue with this approach?
I report my experience with B2K and Istio.
My AKS cluster injects an Istio proxy in each pod to isolate the main app container.
If deployment replicas are set to 1, then B2K works as expected - at least debugging, I didn't push forward yet.
However, if I have more than a replica (2 in my case) it correctly spins up the first container but fails with the second one due to a readyness probe failure - Request to probe app failed: connect: connection refused
Is there any workaround for this?
@Krusty93 can you share the logs ? it would be helpful to triage further.
@Krusty93 can you share the logs ? it would be helpful to triage further.
I am sorry but at time of your reply I had already changed company, so I lost any access to logs