-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Fix kubernetes path prefix rule with rewrite-target #2461
Conversation
f2e27b4
to
fbca00e
Compare
I think this makes sense. @dtomcej @emilevauge WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch @cheungpat!
LGTM
I approved because I can't think that the code would be intended to function the way it was written :P I assume that @cheungpat's PR was what was intended. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with same reasoning as @dtomcej said.
@ldez do we plan to make another 1.4 patch release, or is it okay to let the fix go into the upcoming 1.5 / master? |
When rewrite-target is specified, any existing PathPrefix rule is removed. Hence an ingress with rewrite-target is always matched for the same host regardless of path prefix.
fbca00e
to
6fa6491
Compare
Thanks for merging the pull request! |
When rewrite-target is specified, any existing PathPrefix rule is
removed. Hence an ingress with rewrite-target is always matched
for the same host regardless of path prefix.