-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting ARGOCD_ENABLE_DYNAMIC_CLUSTER_DISTRIBUTION
results in error updating the sharding config map %!s(<nil>)
#16349
Comments
@ishitasequeira, I am hoping to get your insights! Maybe I've missed something in my setup. |
I just deployed v2.9.3 and started running into this. Hoping for a fix soon. |
Thanks @morey-tech for reporting the issue. I think I missed this issue. I will take a look. |
I went through the error message. The error shown is an expected message when the configmap has been updated by another controller while the current controller is trying to update the configmap. I will update the message so that it does not show up as an error and more as an expected message. |
@ishitasequeira, when I install a fresh instance of Argo CD with this kustomization, which includes the Deployment and the env var enabled, the
With the same error as in the issue.
Despite the configmap has only been updated by these controller deployments:
Should the controller exit after that error message? |
I am installing ArgoCD via helm-chart, how do I utilize that Kustomization? |
Thanks @morey-tech !! I was able to reproduce the bug finally. The bug seems to come post the introduction of |
@morey-tech I have raised the PR #16984 for the fix. |
Checklist:
argocd version
.Describe the bug
When using the dynamic cluster shard re-balancing feature, setting
ARGOCD_ENABLE_DYNAMIC_CLUSTER_DISTRIBUTION
totrue
results in theapplication-controller
Deployment
failing to start due to an error updating the shardingConfigMap
. It appears that theConfigMap
name becomes empty in theapplication-controller
logic, as it's trying to update%!s(<nil>)
.Interestingly, setting to
false
or simply removing theARGOCD_ENABLE_DYNAMIC_CLUSTER_DISTRIBUTION
env var results in theargocd-app-controller-shard-cm
ConfigMap
getting updated correctly.To Reproduce
Install Argo CD with this kustomization, which includes the Deployment and the env var enabled.
Expected behavior
The
application-controller
Deployment
should correctly determine the ConfigMap to use for the shard mapping.Screenshots
The configmap being correctly used by the previous replicaset with the env var disabled.
Version
Logs
The text was updated successfully, but these errors were encountered: