-
Notifications
You must be signed in to change notification settings - Fork 766
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
feat: 💥 rework and allow update of namespace policy for Gateway #927
Conversation
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.
Interesting, thanks for this !
My suggestion is for convenience and is not mandatory.
For merging this PR, test on this support are needed (and mandatory).
Ok, @mloiseleur I pushed a new commit with your suggestion and enabled test support. |
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
@renebarbosafl Since it's a parameter of EDIT: or move all |
Co-authored-by: Michel Loiseleur <[email protected]>
@mloiseleur Sure! I pushed a new commit moving everything from |
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.
Many thanks @renebarbosafl.
It's a breaking change and it's clearly better.
Are you ok with the title of the PR ?
You're welcome, @mloiseleur |
What does this PR do?
Enable support for configuring allowedRoutes within a gateway Listener
Motivation
When using this helm chart and integrating with kubeVela we found that It's not working properly (was breaking http-route traits) because the default policy is hardcoded as "Same" and the helm chart does not have the option to configure it as convenience so I've added this option.
More
make test
and all the tests passed