Philipp Plotnikov

@som-kanade-zepto did you check the logs of Kong controller and argo rollouts controller ? Did you see any errors or warnings there ?

Is it similar to create these 2 HTTPRoutes ```yaml kind: HTTPRoute apiVersion: gateway.networking.k8s.io/v1beta1 metadata: name: test-httproute annotations: konghq.com/strip-path: 'true' spec: parentRefs: - kind: Gateway name: kong rules: - matches: -...

I created and it seems both routes work: one that work using argo rollouts and another without argo rollouts. Both uses the same gateway

Ah, I am using Kong of 3.6 version. I will try to downgrade and check will it work or not

@som-kanade-zepto all works, but it needs to add / at ther end of the path so it works for /test/ not /test /api/v1/cart/ not /api/v1/cart

I follow this instruction to install kong https://docs.konghq.com/kubernetes-ingress-controller/latest/install/helm/ After it needs to install argo rollouts with plugin and routes

@som-kanade-zepto did you follow these instructions to install kong ? If not, can you try it, please ?

@som-kanade-zepto as quick check can you upgrade kong and check will it work, please ? Maybe it was a bug in kong(not sure). As for now I dont have any...

> Yes @Philipp-Plotnikov We did install Are you sure you installed following the instructions in the link higher ? As in README the links point to the old doc version.

@som-kanade-zepto old API stopped to work when argo rollouts finishes canary ? Can it be so situation that old routes point to the old pods that were deleted during canary...