Multiple Kong proxy helm deployment with different ingress classes is not routing traffic correctly

[Shubh]

I have below setup:-

Kong-Green:-

1. Kong-green helm deployment - helm upgrade --install kong-green -f green-values.yaml / --namespace kong-green --set fullnameOverride=kong-green --wait --timeout 300s --debug | kong-ingress-class: kong-green

2.Kong ingress as glb - kubernetes.io/ingress.class: gce | BackendConfig: kong-http-hc-config-green (This is for create gcp glb for kong-proxy service)

3. Apps-green: namespace to deploy microservices ex. auth-service-blue | ingressclass: kong-green

Kong-Blue:-

1. Kong-blue helm deployment - helm upgrade --install kong-blue -f blue-values.yaml / --namespace kong-green --set fullnameOverride=kong-blue --wait --timeout 300s --debug | kong-ingress-class: kong-blue

2.Kong ingress as glb - kubernetes.io/ingress.class: gce | BackendConfig: kong-http-hc-config-blue (This is for create gcp glb for kong-proxy service)

3. Apps-Blue: namespace to deploy microservices ex. auth-service-blue | ingressclass: kong-blue

I am facing issues related to routing traffic. Below are the scenarios:-

1. blue endpoint works but green doesn’t
2. Blue works and green works in round robin
3. Other cluster with kong with all resources isolated and named different stops to work.