F44 Change Proposal: Helm4 [SelfContained]

Wiki: https://fedoraproject.org/wiki/Changes/Helm4

Discussion Thread: https://discussion.fedoraproject.org/t/174934

**This is a proposed Change for Fedora Linux.**
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

== Summary ==

Helm 4 has been released upstream with intentional backwards-incompatible changes relative to Helm 3. To ensure a smooth transition for Fedora and EPEL users, this Change introduces Helm 4 as the default `helm` package in Fedora Rawhide, while providing a parallel-installable `helm3` package for users and tooling that still rely on Helm 3.

Helm 3 will continue to be available and maintained as `helm3` in Fedora and EPEL, while the `helm` package will track the latest major release (Helm 4 going forward).

== Owner ==

* Name: [[User:mikelo2| Mikel Olasagasti]]
* Email: mikel@olasagasti.info

== Detailed Description ==

Upstream Helm 4 introduces breaking changes in CLI behavior, chart handling, and release workflow compatibility compared to Helm 3. Many users in CI/CD, Kubernetes automation, and cluster operators still depend on Helm 3's behavior and may not be immediately able to migrate.

Upstream has committed to maintaining Helm 3 with bug fixes until 2026-07-08 and with security fixes until 2026-11-11. To provide Fedora users with a stable transition period, both versions will be shipped in parallel until upstream support ends.

Package	Version	Binary name	Notes
helm	Helm 4	helm	Default package (tracks latest major upstream)
helm3	Helm 3	helm3	Maintained in Fedora until upstream support ends

=== Planned retirement schedule ===
Helm 3 will remain available in Fedora until upstream ends security support.

Given current Fedora release cadence, this means:
* `helm3` will continue to be shipped through Fedora 44.
* Once Fedora 44 is branched from Rawhide (expected mid-2026), `helm3` may be retired from Rawhide and will not appear in Fedora 45+.

== Feedback ==



== Benefit to Fedora ==

* Keeps Fedora up to date with the latest upstream technology.
* Preserves backward compatibility via `helm3`.
* Reduces upgrade friction for cluster operators and CI/CD automation.
* Allows gradual migration and testing of Helm 4.
* Aligns Fedora with Kubernetes ecosystem direction.

== Scope ==

* Proposal owner (packager):
** Create `helm3` spec based on existing Helm 3 sources.
** Update existing `helm` spec to Helm 4.
** Ensure parallel installability (no conflicting binaries/files).
** Provide clear documentation in package descriptions.
* Release engineering:
** Normal review and acceptance of Change.
** No mass rebuild required.
* Policies and guidelines: No
** This is a Self-Contained Change.
** No system-wide impact beyond the Helm ecosystem.

== Upgrade/compatibility impact ==

* Users upgrading Fedora may find helm now provides Helm 4.
* Scripts and automation depending on Helm 3 must explicitly install `helm3`.
The intent is not to break existing Helm 3 workflows, but to allow Fedora users to adopt Helm 4 when ready.

== Early Testing (Optional) ==

Do you require 'QA Blueprint' support? No

== How To Test ==

<pre>

dnf install helm

helm version  # should report Helm 4

dnf install helm3

helm3 version # should report Helm 3

</pre>

Both versions must be installable simultaneously and functional without file conflicts.

== User Experience ==

Users get the latest major upstream version by default. Those requiring Helm 3 can run:

<pre>

sudo dnf install helm3

</pre>

== Dependencies ==



== Contingency Plan ==

* Contingency mechanism: *Not a System-Wide Change.*
** If packaging or testing of Helm 4 is not completed in time, the helm package will remain on Helm 3 and the Helm 4 update will be deferred to the next Fedora release cycle.
** If creation of the helm3 compatibility package is delayed, helm must remain on Helm 3 to avoid breaking user workflows and expectations.
** No forced migration, no Obsoletes/Provides, and no package replacement will occur under contingency.(What to do?  Who will do it?) N/A (not a System Wide Change)

== Documentation ==

N/A (not a System Wide Change)

== Release Notes ==