Helm Charts for Shared Platforms
Values layering, schema validation, and upgrade notes when dozens of teams consume your chart.
You maintain a fictional platform chart with semver discipline, jsonschema for values, and consumer-facing upgrade notes that reduce Slack pings.
What the syllabus includes
- Values layering patterns (base + env + tenant)
- helm schema validation authoring
- Post-render hook trade-offs
- Chart testing with ephemeral clusters
- Consumer comms template for breaking changes
- Deprecating fields without silent failures
- Office hour on chart sprawl intervention
Artifacts you leave with
- Ship a chart minor bump with schema guard and notes
- Author consumer-facing upgrade steps for a breaking values rename
- Identify two chart smells in a provided repo and fix one
Lead mentor
Helene Vogt — Internal platform chart maintainer; likes boring changelogs.
Duration: 4 weeks · mixed async · Format: self-paced · Category: portfolio projects · Level: intermediate
Price (informational): 8,600 THB — see Money-Back Policy for eligibility notes.
FAQ
We pick Helm for shared chart scenarios; Kustomize noted where it fits better.
Auth patterns described; no vendor-specific paid features.
Operator SDK chart generation is excluded.
Participant notes
Helm Charts for Shared Platforms jsonschema lab cut our bad values deploys noticeably.