3pp-mirror/pomerium
1
0
Fork 0
mirror of https://github.com/pomerium/pomerium.git synced 2025-08-03 16:59:22 +02:00
Code Issues Projects Releases Packages Wiki Activity

Docs: Ingress routing order (#3077)

Browse source 
* document routing order

* Update docs/docs/k8s/ingress.md

Co-authored-by: Alex Fornuto <afornuto@pomerium.com>

* Update docs/docs/k8s/ingress.md

Co-authored-by: cmo-pomerium <91488121+cmo-pomerium@users.noreply.github.com>
This commit is contained in:
Alex Fornuto 2022-03-08 14:32:39 -06:00 • committed by GitHub
parent 9e4edb8003
commit 01391a6055
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/docs/k8s/ingress.md
View file

@ -124,6 +124,18 @@ metadata:
:::
::: tip
Routes are sorted and applied in the following order.
1. Ascending by `from`.
1. Descending by `path`.
1. Descending by `regex`.
1. Descending by `prefix`.
1. Ascending by `id`.
This sorting order helps ensure that more restrictive routes for specific paths and regexes are applied correctly.
:::
### Supported Annotations
Most configuration keys in non-Kubernetes deployments can be specified as annotation in an Ingress Resource definition. The format is `ingress.pomerium.io/${OPTION_NAME}`. The expandable list below contains the annotations available, which behave as described in our reference documentation (with links to the appropriate reference documentation).