ArgoCD reports a warning about imperative-admin-sa appearing twice during sync. This happens because our values-coco-dev.yaml sets serviceAccountName: imperative-admin-sa, which collides with the framework's default adminServiceAccountName (also imperative-admin-sa). The clustergroup template then tries to create the same ServiceAccount twice.
The warning is harmless and does not break anything, but it should be cleaned up. The fix likely involves either keeping the default imperative-sa name and granting it the necessary permissions, or adjusting how the framework handles the case where both names are identical.
ArgoCD reports a warning about
imperative-admin-saappearing twice during sync. This happens because our values-coco-dev.yaml setsserviceAccountName: imperative-admin-sa, which collides with the framework's defaultadminServiceAccountName(alsoimperative-admin-sa). The clustergroup template then tries to create the same ServiceAccount twice.The warning is harmless and does not break anything, but it should be cleaned up. The fix likely involves either keeping the default
imperative-saname and granting it the necessary permissions, or adjusting how the framework handles the case where both names are identical.