Elgato_dark/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd synced 2026-05-23 09:18:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

docs: Improved documentation for Ambassador host-based routing configuration (#4857)

Browse source 
Signed-off-by: alex <alex@datawire.io>
This commit is contained in:
Alex Gervais 2020-11-18 17:06:03 -05:00 committed by GitHub
parent ed547aa545
commit 6e6f4f50a0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/operator-manual/ingress.md
View file

@ -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 <host>:<port> --grpc-web-root-path /
```
### Option 2: Mapping CRD for Path-based Routing