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
IngressRoute: add an option to disable cross-namespace routing #7595
Conversation
@jbdoumenjou, @rtribotte Could you add a new integration test? |
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.
just some minor stuff :)
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
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 👍
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 👍
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
Co-authored-by: Harold Ozouf <harold.ozouf@gmail.com> Co-authored-by: Manuel Zapf <me@manuelzapf.io>
What does this PR do?
This PR adds the
allowCrossNamespace
option on the Kubernetes provider configuration to allow/disallow cross-namespace routing.The
allowCrossNamespace
is defaulted totrue
.When set to
false
it's not possible for an IngressRoute to reference a service in another namespace than its namespace.Motivation
fixes #7353
More
Additional Notes
Co-authored-by: Jean-Baptiste Doumenjou 925513+jbdoumenjou@users.noreply.github.com