From 71c1f549c4e8e6023c8bfe8e8e5033b64c5b65a2 Mon Sep 17 00:00:00 2001 From: noah Date: Thu, 30 Jun 2022 11:20:37 -0500 Subject: [PATCH] docs: custom secret must be labeled (#9835) As far as I can tell, this isn't explicitly documented anywhere (some docs mentioned this label in reference to ConfigMaps) I only figure it out by looking at the code. --- docs/operator-manual/user-management/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/operator-manual/user-management/index.md b/docs/operator-manual/user-management/index.md index 3aaa60f88aab4..baa08269cf003 100644 --- a/docs/operator-manual/user-management/index.md +++ b/docs/operator-manual/user-management/index.md @@ -197,6 +197,7 @@ NOTES: * There is no need to set `redirectURI` in the `connectors.config` as shown in the dex documentation. Argo CD will automatically use the correct `redirectURI` for any OAuth2 connectors, to match the correct external callback URL (e.g. `https://argocd.example.com/api/dex/callback`) +* When using a custom secret (e.g., `some_K8S_secret` above,) it *must* have the label `app.kubernetes.io/part-of: argocd`. ## OIDC Configuration with DEX