6321442a01
* Better Helm chart NOTES.txt templating Add some extra templating to NOTES.txt, which are displayed to the user after a successful helm install command. These are really helpful notes, but if you didn't specify a release name of argocd or put it in a separate namespace, these commands weren't exactly working with a copy paste. Now they should take into account the release name and release namespace helm was given. * Small CONTRIBUTING.md command line change Instead of just doing `argocd version`, be a little more explicit by passing in the server name and insecure flag. This will make sure that you're doing the version of the instance you're port-forwarding above, as opposed to some other argocd.
15 lines
1,022 B
Text
15 lines
1,022 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 `service.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
|