Skip to content
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

Implement Gateaway Listener allowedRoutes.namespaces #2389

Merged
merged 7 commits into from
Apr 18, 2022

Commits on Apr 11, 2022

  1. feat(gateway) implement listen namespace filters

    Implement the allowedRoutes.RouteNamespaces filters, which instruct
    listens to only accept routes in a specific set of namespaces.
    rainest committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    4f3d25b View commit details
    Browse the repository at this point in the history
  2. chore(tests) remove --watch-namespaces

    Remove --watch-namespaces from the test arguments, to allow tests that
    create additional namespaces beyond their standard test namespace.
    rainest committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    5e65b47 View commit details
    Browse the repository at this point in the history
  3. feat(gateway) merge user allowedRoutes

    Merge the allowedRoutes configuration for Gateway listeners into the
    generated managed Gateway listeners. If a user listen has the same
    protocol as a generated listener, add the user listener's allowedRoutes
    section into the generated listener.
    rainest committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    52d593b View commit details
    Browse the repository at this point in the history
  4. feat(gateway) restrict listeners to type

    When looking for a supported gateway, only check the listeners whose
    protocol matches the route type.
    rainest committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    8efcb6b View commit details
    Browse the repository at this point in the history
  5. feat(gateway) confirm valid AllowedRoute

    Check that AllowedRoutes from user-provided Listeners meet the criteria
    necessary for Kong: Listeners for the same protocol must not specify
    different filter requirements because Kong combines all routes into a
    single proxy configuration.
    rainest committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    ec9b0c1 View commit details
    Browse the repository at this point in the history

Commits on Apr 15, 2022

  1. Apply suggestions from code review

    Co-authored-by: Shane Utt <shaneutt@linux.com>
    rainest and shaneutt committed Apr 15, 2022
    Configuration menu
    Copy the full SHA
    d1e789a View commit details
    Browse the repository at this point in the history

Commits on Apr 18, 2022

  1. Configuration menu
    Copy the full SHA
    46151c9 View commit details
    Browse the repository at this point in the history