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

Ingess V2 #51

Merged
merged 11 commits into from
Oct 12, 2024
Merged

Ingess V2 #51

merged 11 commits into from
Oct 12, 2024

Conversation

murillio4
Copy link
Contributor

Update how we define ingress.

Ingress config now looks like this:

ingress:
  routes: #Can be null, or list of ingresses
    - host: example.com #Hostname that should be mapped
      path: /test #Nullable path that should be matched. Can be regex if starts with 're:'
      headers: #Nullable map of headers that should match. Value can be regex if starts with 're:'
        some-header: some-value
      queries: #Nullable map of queries that should match. Value can be regex if starts with 're:'
        isRegex: re:starts-with.*
      middlewares: #Nullable list of middlewares that should be applied to route
      - some-middleware
  middlewares: #Nullable list of middlewares that should be applied to all routes. Will be applied first
    - another-middleware

@murillio4 murillio4 merged commit 9e75df3 into main Oct 12, 2024
5 checks passed
@murillio4 murillio4 deleted the feature/ingress-v2 branch October 12, 2024 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant