9e6d1134e8
* chore(argo-cd): Fix ingress configuration in helm notes (#526) Signed-off-by: arndt-s <17650715+arndt-s@users.noreply.github.com>
15 lines
1,019 B
Text
15 lines
1,019 B
Text
In order to access the server UI you have the following options:
|
|
|
|
1. kubectl port-forward service/{{include "argo-cd.fullname" . }}-server -n {{ .Release.Namespace }} 8080:443
|
|
|
|
and then open the browser on http://localhost:8080 and accept the certificate
|
|
|
|
2. enable ingress in the values file `server.ingress.enabled` and either
|
|
- Add the annotation for ssl passthrough: https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md#option-1-ssl-passthrough
|
|
- Add the `--insecure` flag to `server.extraArgs` in the values file and terminate SSL at your ingress: https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md#option-2-multiple-ingress-objects-and-hosts
|
|
|
|
|
|
After reaching the UI the first time you can login with username: admin and the password will be the
|
|
name of the server pod. You can get the pod name by running:
|
|
|
|
kubectl get pods -n {{ .Release.Namespace }} -l app.kubernetes.io/name={{ include "argo-cd.name" . }}-server -o name | cut -d'/' -f 2
|