At the company that I’m working on, we’re trying to replace our legacy API gateway. I’ve been migrating service by service using the Istio HTTP routing capabilities. When a given endpoint hit the legacy API gateway like /v1/documents I simply send it to the new one. The idea is to do this until every endpoint is migrated.
Long story short, what I have now is the requests being sent to both services. Not shadowing the traffic, actually acting like a load balancer, but not properly a load balancer because the requests are not equally balanced. Is more like the bulk of the requests are going to the new gateway while some still hit the old one.
There is any way to debug this feature in order to understand the problem?
My actual configuration at the legacy API gateway looks like this:
{
"apiVersion": "networking.istio.io/v1beta1",
"kind": "VirtualService",
"spec": {
"gateways": [
"api-gateway"
],
"hosts": [
"api.company.com"
],
"http": [
{
"match": [
{
"ignoreUriCase": true,
"uri": {
"prefix": "/v1/events"
}
},
{
"ignoreUriCase": true,
"uri": {
"prefix": "/v1/documents"
}
},
{
"uri": {
"regex": "(?i)^\\/v1\\/users\\/.*\\/documents"
}
}
],
"route": [
{
"destination": {
"host": "new-api-gateway.svc.cluster.local",
"port": {
"number": 80
}
}
}
]
},
{
"route": [
{
"destination": {
"host": "old-api-gateway.svc.cluster.local",
"port": {
"number": 80
}
}
}
]
}
]
}
}