ApplicationSet tokenRef strict mode changes only apply after the controller is restarted
維護者通常 1 天內回覆
評估
這個 Issue 還沒有評估資料。
描述
Describe the bug
While working on #1551 I noticed that changing the ApplicationSet tokenRef strict mode on an existing instance has no effect until the ApplicationSet controller Pod is restarted, and the operator doesn't restart it.
The operator writes applicationsetcontroller.enable.tokenref.strict.mode to argocd-cmd-params-cm, and the controller Deployment reads it through a configMapKeyRef (argocd-operator/controllers/argocd/applicationset.go). The controller only reads that variable when it starts, and the Deployment spec is the same for both values, so a change in the ConfigMap never rolls it out.
Two things follow from that:
- The opt-out described in
docs/usage/appsets-in-any-namespace.md(.spec.cmdParamsset to"false") does nothing until someone restarts the Pod. The docs don't mention a restart. - The other direction is the one that worries me. After the opt-out is removed, the CR and the ConfigMap say strict mode is on, but the controller keeps reading unlabeled Secrets through
tokenRefuntil its next restart.
To Reproduce
I ran this on a kind cluster, with the operator running from master (8f72660b) and the default Argo CD image (v3.5.6).
-
Create a cluster-scoped instance with ApplicationSets in any namespace:
apiVersion: argoproj.io/v1beta1 kind: ArgoCD metadata: name: argocd namespace: openshift-gitops spec: sourceNamespaces: [tr-bar] applicationSet: sourceNamespaces: [tr-bar] scmProviders: ["https://gitlab.invalid"] -
In
tr-bar, create a Secretscm-tokenwithout theargocd.argoproj.io/secret-type: scm-credslabel, and an ApplicationSet with a Pull Request generator that uses it:generators: - pullRequest: gitlab: project: "1" api: https://gitlab.invalid tokenRef: secretName: scm-token key: tokenThe ApplicationSet reports
secret tr-bar/scm-token is not a valid SCM creds secret, as it should. -
Set
applicationsetcontroller.enable.tokenref.strict.mode: "false"in.spec.cmdParamsand wait for the ConfigMap to change. Recreate the ApplicationSet: the Secret is still refused. -
Run
kubectl rollout restart deploy/argocd-applicationset-controller. Now the opt-out is live: the error becomesdial tcp: lookup gitlab.invalid ... no such host, so the token was read and the provider was called with it. -
Remove the key from
.spec.cmdParamsand wait for the ConfigMap to go back totrue. Recreate the ApplicationSet: the unlabeled Secret is still read.
This is what I saw at each step. The Pod was the same one from step 4 until I restarted it again:
| Step | .spec.cmdParams |
ConfigMap | Env in the running Pod | Unlabeled Secret |
|---|---|---|---|---|
| 2 | not set | true |
true |
refused |
| 3, 60s after the ConfigMap changed | false |
false |
true |
refused |
| 4, after the manual restart | false |
false |
false |
read |
| 5, 60s after the ConfigMap changed | not set | true |
false |
read |
| 5, three minutes later | not set | true |
false |
read |
| after another manual restart | not set | true |
true |
refused |
Expected behavior
A change in the effective strict mode value reaches the ApplicationSet controller without a manual restart, in both directions.
Additional context
- Adding
sourceNamespacesto an existing instance works. The Deployment command changes in the same reconcile, so the Pod is replaced, and it came up with strict mode on the three times I tried. - The E2E tests for this feature (
1-037) check the value in the ConfigMap, not what the controller does, so they pass. - I didn't test on OpenShift or with an OLM install, only with the operator running from source against kind.
A possible fix is to set the value on the container from the same logic that fills the ConfigMap, so that a change in the value changes the Deployment. That's what #1551 does for server.disable.swagger.ui. I'm happy to send a PR with unit and E2E tests if that sounds right to you.
- 主要語言
- Go
- 星號
- 190
- 分支
- 367
- 平均合併
- 4 天 2 小時
- 30 天內合併 PR
- 63
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
redhat-developer/gitops-operator 的其他 Issue
-
Manager does not detect Route CRD that appears after startup可能已有人在做 @atishay-kasliwal 今天認領。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
redhat-developer/gitops-operator#1566 · 1 則留言 ·
維護者通常 1 天內回覆
-
NamespaceManagement revocation checks labels on the wrong namespace可能已有人在做 @Rizwana777 於 3 天前認領。 未關閉kind/bug
難度 4/5 3-5 天 新手友好度 25/100
redhat-developer/gitops-operator#1559 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Deleting an ArgoCD instance removes RBAC belonging to same-named instances可能已有人在做 @Rizwana777 於 3 天前認領。 未關閉kind/bug
難度 3/5 1-2 天 新手友好度 45/100
redhat-developer/gitops-operator#1558 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
NamespaceManagement cleanup can delete RBAC in unrelated namespaces可能已有人在做 @Rizwana777 於 3 天前認領。 未關閉kind/bug
難度 4/5 3-5 天 新手友好度 22/100
redhat-developer/gitops-operator#1557 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Enqueue the previous Argo CD instance when NamespaceManagement consent is withdrawn可能已有人在做 @Gabrielandre02 於 5 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 25/100
redhat-developer/gitops-operator#1530 · 1 則留言 ·
維護者通常 1 天內回覆
查看 redhat-developer/gitops-operator 的全部 Issue
相似的 Issue
-
benchmark
難度 1/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 77/100
mozilla-ai/cq#601 ·
維護者通常 1 天內回覆
-
documentation migration
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆