Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Since Helm v4 was released upstream, we need to support in OpenShift as well.
We will ship two CLIs per Helm version (v3 and v4) available for download and ensure our console is adjusted to support Helm v4.

We will also provide a compatibility matrix for Helm versions vs OpenShift version to make it clear for customers what is supported where.

Goals:

Implement support for Helm4 in OpenShift in both CLI and Console.

Provide support matrix between Helm and OpenShift versions and allow time for customers to migrate.

Consider support for chart v3 APIs. 

Not in scope:

Migration tooling from v3 to v4.

Additional information:

Helm 4 was released on Nov 12 2025, and Helm 3 will be deprecated by the community on :

• Bug fixes until July 8th 2026.
• Security fixes until November 11th 2026.

Requirements also discussed on this meeting.

 ----- copied from RFE-8707 -----
1. Proposed title of this feature request

helm v4 compatible with Openshift

2. What is the nature and description of the request?

Before the end of 2026 helm v3 will be EoL.
Helm v3 continued support dates:

• Bug fixes until July 8th 2026
• Security fixes until November 11th 2026

The ask here is to get helm v4 compatible with OCP x.y releases that will be on deployments beyond EoL of helm v3. The general idea would be:

• Have an OpenShift release that supports both Helm v3 and Helm v4.
• Announce a clear timeline and deprecation plan.
• Require applications to adopt Helm v4 within a defined timeframe.

3. Why does the customer need this? (List the business requirements here)

Customer applications are currently deployed on Openshift using helm v3 charts and they will eventually migrate to helm v4.

4. List any affected packages or components.
OCP API server.
 ------------------------------------------------------

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

 This Feature was generated in OCPSTRAT via acceptance of RFE-8707. Ensure the stated Acceptance Criteria below will fulfill the needs specified in the RFE.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>