GitOps Hub Bottlenecks Predicted by Object Volume, Not Cluster Count

Argo CD application controllers hit out-of-memory failures around 15,000 to 20,000 cached objects per hub, according to large-scale testing. Sharding and tuning delayed limits but didn't remove the underlying memory cost. A centralized model holding state becomes the bottleneck, while distributed architectures like Sveltos used about 2 GB versus Argo CD's 21 GB in one scenario.