From 3e3977a51452be2daddda3bcbb40551555f8e15c Mon Sep 17 00:00:00 2001 From: Matt Farina Date: Thu, 9 Jan 2025 12:04:40 -0500 Subject: [PATCH] Adding a HIP on charts v3 Signed-off-by: Matt Farina --- hips/hip-0000.md | 77 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 hips/hip-0000.md diff --git a/hips/hip-0000.md b/hips/hip-0000.md new file mode 100644 index 00000000..234ffb26 --- /dev/null +++ b/hips/hip-0000.md @@ -0,0 +1,77 @@ +--- +hip: 9999 +title: "H4HIP: Charts v3 Enablement" +authors: [ "Matt Farina " ] +created: "2025-01-09" +type: "feature" +status: "draft" +--- + +## Abstract + +This HIP proposes the creation of charts v3, updating Helm to handle charts v2 and v3, and a +timeline for the general availability of charts v3 that can happen after the release of Helm v4.0.0. + +## Motivation + +Many of the proposed changes for Helm v4 affect charts. Layering these onto existing charts will +sometimes cause chart installation and upgrade to happen differently in Helm v3 and Helm v4, as +both will need to live side by side for a time. It also means that testing of charts for v3 can produce +a different result when installed with Helm v4. + +In addition to the affects of the changes, Helm v4 development has a fixed timeline and making +changes to Helm in addition to reworking charts is not likely to fit within that fixed window. Enabling +the development of charts v3 to happen as an experiment that becomes generally available after +the release of Helm v4 provides more time to continue the work and get feedback. + +The goal is to provide adequate time to work on chart changes while doing it in a way that enables +trust in existing charts to run as they were tested. + +## Rationale + +Charts v2 were created for Helm v3 and introduced minor changes. The code that handles the chart +versions is the same with some checking to handle the differences. This handling ended up having +numerous bugs that had to be worked out in patch releases. + +The chart changes being proposed for Helm v4 are more significant. Mixing those in alongside the +current chart version handling will have trouble limiting bugs will enabling the changes and keeping +existing charts functioning properly. + +The design specified here is meant to enable the current charts to work as expected while providing +space for more radical changes. + +## Specification + +Describe the syntax and semantics of any new feature. + + + +## Backwards compatibility + +Describe potential impact and severity on pre-existing code. + +## Security implications + +How could a malicious user take advantage of this new feature? + +## How to teach this + +How to teach users, new and experienced, how to apply the HIP to their work. + +## Reference implementation + +Link to any existing implementation and details about its state, e.g. +proof-of-concept. + +## Rejected ideas + +Why certain ideas that were brought while discussing this HIP were not +ultimately pursued. + +## Open issues + +Any points that are still being decided/discussed. + +## References + +A collection of URLs or materials used as references through the HIP. \ No newline at end of file