We analyzed thousands of Helm charts from Artifact Hub to find the most common patterns, values, and conventions. Build better charts backed by real data.
image.repositoryThese are the value paths used most frequently across all analyzed charts. Following these patterns helps your charts feel familiar to users.
image.repositoryUsed in 78% of chartsimage.tagUsed in 76% of chartsservice.typeUsed in 71% of chartsreplicaCountUsed in 68% of chartsresources.limits.cpuUsed in 64% of chartsWhen your chart uses common patterns like image.repository and service.type, users know exactly what to expect. No documentation needed for basic configuration.
Many tools and platforms expect standard value names. Using conventions like replicaCountand resources.limits means your charts work seamlessly with monitoring, GitOps, and CI/CD tools.
Engineers switch between charts constantly. Following the same patterns across all charts means less time reading docs, less mental overhead, fewer mistakes.
When you follow standards, the vast knowledge base of Helm tutorials, Stack Overflow answers, and blog posts becomes directly applicable to your chart.
A deep dive into the value paths that appear in the majority of Helm charts, what they're used for, and how to implement them correctly in your own charts.
Should it be imagePullPolicy or image.pullPolicy? We analyzed thousands of charts to find out what actually works in practice.
A practical guide to creating Helm charts that follow community standards, with templates and examples you can use immediately.