From 6e6f4f50a0f0b04c5b85dfe44bfdbc5de4029b5a Mon Sep 17 00:00:00 2001 From: Alex Gervais Date: Wed, 18 Nov 2020 17:06:03 -0500 Subject: [PATCH] docs: Improved documentation for Ambassador host-based routing configuration (#4857) Signed-off-by: alex --- docs/operator-manual/ingress.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/docs/operator-manual/ingress.md b/docs/operator-manual/ingress.md index 8f8ef79163..0eec0dee7f 100644 --- a/docs/operator-manual/ingress.md +++ b/docs/operator-manual/ingress.md @@ -12,19 +12,35 @@ There are several ways how Ingress can be configured. The Ambassador Edge Stack can be used as a Kubernetes ingress controller with [automatic TLS termination](https://www.getambassador.io/docs/latest/topics/running/tls/#host) and routing capabilities for both the CLI and the UI. -The API server should be run with TLS disabled. Edit the `argocd-server` deployment to add the `--insecure` flag to the argocd-server command. +The API server should be run with TLS disabled. Edit the `argocd-server` deployment to add the `--insecure` flag to the argocd-server command. Given the `argocd` CLI includes the port number in the request `host` header, 2 Mappings are required. ### Option 1: Mapping CRD for Host-based Routing ```yaml apiVersion: getambassador.io/v2 kind: Mapping metadata: - name: argocd-server + name: argocd-server-ui namespace: argocd spec: host: argocd.example.com prefix: / service: argocd-server:443 +--- +apiVersion: getambassador.io/v2 +kind: Mapping +metadata: + name: argocd-server-cli + namespace: argocd +spec: + host: argocd.example.com:443 + prefix: / + service: argocd-server:443 +``` + +Login with the `argocd` CLI using the extra `--grpc-web-root-path` flag for gRPC-web. + +```shell +argocd login : --grpc-web-root-path / ``` ### Option 2: Mapping CRD for Path-based Routing