Helm Chart Strategy for a 40+ Services — Looking for Expert Inputs Hey folks, I'm a Platform Engineer. We have 40+ microservices across four business domains, but it's part of a product. We've been thinking hard about how to structure our Helm charts and GitOps setup, and I wanted to get inputs from people who've dealt with similar scale. \--- \*\*Our Architecture\*\* \- 40 repos → 45+ Docker images → 45+ pods \- Services are grouped into 4 domains \- Mix of HTTP and gRPC services \--- \*\*Questions I'm Wrestling With\*\* 1. \*\*Generic chart complexity\*\* — At what point does a single generic chart become too complex to maintain? When would you draw the line and spin off a separate chart? 2. \*\*Domain chart value\*\* — Is grouping services into section charts worth the extra layer, or is it over-engineering ? 3. \*\*Release strategy\*\* — We're thinking one root chart version bump = full product release. Has anyone done atomic releases like this at scale?…