Skip to content

Commit

Permalink
Doc nginx passthrough secret as argocd-server-tls
Browse files Browse the repository at this point in the history
As documented in tls.md § "TLS certificates used by argocd-server", the secret that should be modified by cert-manager is not `argocd-server` but `argocd-server-tls` should be created instead.

The ingress-nginx controller doesn't like using a secret of `type: Opaque`.

Signed-off-by: Josh Gardner <111776680+jdg-journeyfront@users.noreply.github.com>
  • Loading branch information
jdg-journeyfront committed Mar 17, 2023
1 parent 91aff09 commit ad6275e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/operator-manual/ingress.md
Original file line number Diff line number Diff line change
Expand Up @@ -240,7 +240,7 @@ spec:
tls:
- hosts:
- argocd.example.com
secretName: argocd-secret # do not change, this is provided by Argo CD
secretName: argocd-server-tls # as expected by argocd-server
```

### Option 2: Multiple Ingress Objects And Hosts
Expand Down

0 comments on commit ad6275e

Please sign in to comment.