Skip to content

Upgrade helm due to high CVE #12386

Open
@vdveldet

Description

@vdveldet

What happened?

Due to high rated CVE
helm needs version 3.18.4 or higher

What did you expect to happen?

The below command

helm version 
version.BuildInfo{Version:"v3.16.4", GitCommit:"7877b45b63f95635153b29a42c0c2f4273ec45ca", GitTreeState:"clean", GoVersion:"go1.22.7"}

should display 3.18.4 or higher

How can we reproduce it (as minimally and precisely as possible)?

Add helm helm_enabled: True then check the version on a control node.

OS

RHEL 9

Version of Ansible

ansible --version
ansible [core 2.16.14]
  config file = None
  configured module search path = ['/home/runner/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
  ansible collection location = /home/runner/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.10.12 (main, May 27 2025, 17:12:29) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.1.6
  libyaml = True

Version of Python

3.10.12

Version of Kubespray (commit)

2.28.0

Network plugin used

calico

Full inventory with variables

helm_enabled: True

Command used to invoke ansible

anible-playbook cluster.yaml -i inventory/hosts.yaml

Output of ansible run

The playbook run is working

Anything else we need to know

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    RHEL 9kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions