Skip to content

Support Helm provider version 3.x #484

@moko-poi

Description

@moko-poi

Community Note

  • Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

I would like to use Helm provider version 3.x with this module. Currently, the module has a version constraint that pins the Helm provider to version 2.x (likely >= 2.4.1, < 3.0.0), which was implemented in #453 to address breaking changes. This constraint prevents users from upgrading to Helm provider 3.x in their Terraform projects.

Helm provider 3.x is now the latest major version and includes important bug fixes, performance improvements, and long-term support.

Describe the solution you would like

Update the versions.tf file to support Helm provider version 3.x:

  • Remove or update the upper version constraint on the Helm provider
  • Test the module for compatibility with Helm provider 3.0+
  • Address any breaking changes introduced in Helm provider 3.x
  • Update documentation if there are any behavior changes users should be aware of

Example version constraint:

helm = {
  source  = "hashicorp/helm"
  version = ">= 2.4.1"  # or ">= 3.0.0" if dropping support for 2.x
}

Describe alternatives you have considered

Alternative 1: Continue using Helm provider 2.x

  • Downside: Missing out on improvements in 3.x, and 2.x will eventually lose support

Alternative 2: Fork the module and modify version constraints

  • Downside: Maintenance burden, missing upstream updates

Alternative 3: Use a separate Helm provider configuration outside this module

  • Downside: Reduces module functionality, inconsistent infrastructure management

Additional context

This change would allow users to take advantage of the latest Helm provider features while maintaining backward compatibility if possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions