Helm Improvement Proposals (HIPs)
To learn more about the purpose of HIPs and how to go about writing a proposal, please start reading HIP 1.
Markdown for Proposals
Original proposal source should be written in Markdown format, and the format is described in HIP 1. Older proposals were often written in a more mildly restricted markdown format and can be found in the archives.
Existing HIPs
- hip-0001: Writing a HIP
- hip-0002: Pre-defined release dates for Helm
- hip-0003: How Projects Join the Helm Organization
- hip-0004: Document backwards-compatibility rules
- hip-0005: Helm Org Maintainers and Deprecated Projects
- hip-0006: OCI Support
- hip-0007: Document and Track maintainer groups
- hip-0008: Add descriptions to custom completions
- hip-0009: Transitioning Security Team Members on Project Deprecation
- hip-0010: Distributed responsibility for picking
- hip-0011: CRD Handling in Helm 3
- hip-0012: Helm 4 Development Process
- hip-0014: Helm Triage Maintainers
- hip-0015: Annotation for Images used by Helm Charts
- hip-0017: Helm OCI MediaType Registration
- hip-0018: Include repository URL and tarball digest in chart's release metadata
- hip-0019: New annotations for displaying hook output
- hip-0020: H4HIP: Charts v3 Enablement
- hip-0021: Enhanced logging library for Helm
- hip-0022: Wait With kstatus
- hip-0023: Utilize Server Side Apply for installs/upgrades
- hip-0024: Improve the Helm Documentation
- hip-0025: Better Support for Resource Creation Sequencing
- hip-0026: H4HIP: Wasm plugin system
- hip-0027: Bring .helmignore to parity with .gitignore file targeting syntax
- hip-0029: Expose Release History During Template Rendering