Open michalschott opened 1 year ago
As far as I can tell, we only truncate labels if you're using annotation+label
tracking, not just label
. https://github.com/argoproj/argo-cd/blob/master/util/argo/resource_tracking.go#L143-L163
I'm not sure which should be changed, the docs or the implementation. https://argo-cd.readthedocs.io/en/stable/user-guide/resource_tracking/#tracking-kubernetes-resources-by-label
I lean towards changing just the docs. Annotation-based tracking should generally be preferred anyway.
@crenshaw-dev thanks for explanation, I'll give annotation tracking a go.
Please also be sure to upgrade to a more recent version :)
Checklist:
argocd version
.Describe the bug
In my case ArgoCD uses
argocd.argoproj.io/instance: $APP_NAME
to track ownership. In case length of$APP_NAME
exceeds 63 characters kubernetes refuses to create object.I believe this should / could be trimmed on ArgoCD level. Currently the only way to bypass this is by trimming $APP_NAME outside of ArgoCD.
To Reproduce
Expected behavior
Screenshots
Version
2.4.28 (have not checked newer versions, might not be related)
Logs
sync error message: