From 3ba9111e2ca7417d97cad8c1142d0467a5a6432d Mon Sep 17 00:00:00 2001 From: Alex Fornuto Date: Thu, 14 Oct 2021 11:00:22 -0400 Subject: [PATCH] Update docs/docs/k8s/ingress.md Co-authored-by: Travis Groth --- docs/docs/k8s/ingress.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/docs/k8s/ingress.md b/docs/docs/k8s/ingress.md index f09c08542..c3f981e88 100644 --- a/docs/docs/k8s/ingress.md +++ b/docs/docs/k8s/ingress.md @@ -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: