mirror of
https://github.com/pomerium/pomerium.git
synced 2025-06-03 11:22:45 +02:00
Update docs/docs/k8s/ingress.md
Co-authored-by: Travis Groth <travisgroth@users.noreply.github.com>
This commit is contained in:
parent
4dd5f9d65f
commit
3ba9111e2c
1 changed files with 1 additions and 4 deletions
|
@ -75,10 +75,7 @@ TODO: Extrapolate on ^
|
|||
|
||||
### Defining Routes
|
||||
|
||||
If you've tested Pomerium using the all-in-one service, you're probably familiar with configuring routes in Pomerium's `config.yaml`. In this environmenzt, each route is defined as a.... what @travis?
|
||||
|
||||
TODO: Finish ^
|
||||
|
||||
If you've tested Pomerium using the all-in-one service, you're probably familiar with configuring routes in Pomerium's `config.yaml`. In this environment, each route is defined as an Ingress resource in the Kubernetes API.
|
||||
The Ingress Controller will monitor Ingress resources in the cluster, creating a Pomerium route definition for each one. Policy and other configuration options for the route are set by using annotations starting with `ingress.pomerium.io/`.
|
||||
|
||||
Example:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue