-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite annotation causing KIC sync loop #5021
Comments
Rewrite is attached in KIC code on service level instead of route level kubernetes-ingress-controller/internal/dataplane/translator/subtranslator/ingress.go Lines 444 to 474 in 9ad403f
It leads to conflicts as described #5140 (comment) |
@jeffrey-arndt yesterday releases contain a fix for the reported bug |
I'm seeing the same issue with KIC 3.2 + Kong 3.7 on K8s 1.28 and getting the same behaviour. If I have two Ingresses with the same backing service, the rewrite gets applied randomly on requests. When I change the backing services to different ones, the rewrite works properly again. Should I open a new bug? Or will this be tracked here? Any additional data I can provide? |
@herself 👋 Yes, please create a new issue specifically mentioning the version that you use. Can you also try with 3.3 if the issue persists? |
Thanks - unfortunately, it seems to persist on 3.3 as well. Opened #6542, thank you for guidance! |
Is there an existing issue for this?
Current Behavior
Setup:
2 Ingress objects pointing at the same service
1 Ingress with the rewrite annotation
1 Ingress without the annotation
We see that the request transformer plugin is applied at the Service level and the configuration flip flops creating and deleting the plugin in a loop
Video attached showing the behavior:
https://drive.google.com/file/d/1FYwZaSOwT-Lvin9NzTcFN2mnFxds1UAR/view?usp=sharing
Expected Behavior
The the Ingress objects should not conflict causing a scenario where the plugin is deleted/recreated over and over
Additionally, I believe it would be better that the request transformer plugin is applied at the route level. This would allow for more granular configuration
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
No response
The text was updated successfully, but these errors were encountered: