Istio mesh expansion to legacy network

#1

Hi all,

I have a private cloud network (using k8s with istio) and i want to access legacy service on a legacy network.
I want to use mTLS to authentificate pod from k8s and allow it to access legacy service.
How can i do that ?
I thinking about creating a new k8s cluster on the legacy network with istio enabled and create an ingress gateway in it. The goal is that the pod on the cloud will talk to the istio ingress gateway in the legacy network (so we can authentificate and authorize the access to the service in legacy network).
What i don’t know is that: is the istio ingress gateway in the legacy network can forward the traffic to legacy services. And if yes how can i do it ?

0 Likes

#2

An alternate approach to using another cluster or mesh expansion would be to deploy a proxy that can perform as a bridge between Istio and your legacy services. I wrote about this in the following blog post:

The example uses F5 BIG-IP (my employer), but it could work with any proxy capable of mTLS.

1 Like

#3

By legacy network, I assume you mean across different RFC1918 namespace, and does not have direct reachability between k8s pod and vm ips.

Current Istio mesh expansion assume direct IP reachability.

We have across network support for multi cluster, but haven’t done same thing for mesh expansion. We might add that later.

For priority purpose, do you mind commenting on the important of this use case for you?

0 Likes

#4

@incfly no i have direct IP reachability between k8s nodes and the vip of the istio gateway on the “legacy” network (so pods can create mTLS connexion directly to the istio gateway on the “legacy” network).
What i need to know is how to route traffic from my k8s pod to servers on the “legacy” network using the istio gateway.

0 Likes