Application Controller autoscaler+partitioner

[dee-kryvenko]

Hi, I just finished working on a prototype of a data driven and external (to argocd) version of the autoscaler and partitioner. I was wondering if anyone could take a look at my design doc and maybe point me out what I can do better/different: https://github.com/plumber-cd/argocd-autoscaler/blob/main/DESIGN.md

Particularly, the whole notion of managing shard assignments via .data.shard on the secret seem flaky, I do get The cluster https://kubernetes.default.svc has no assigned shard. messages in log, although after short time they are ending up assigned as partitioner assigned them... not sure why would this ever happen

argo-cd/controller/sharding/cache.go

Line 67 in 6daaac5

log.Warnf("The cluster %s has no assigned shard.", c.Server)

considering that the secret was updated prior to the application controller start. Anyway, will appreciate feedback and ideas. Thanks.