Repository navigation
Add helm v3 and v4 to the tooling image (WTO-475) - #87
Merged
Merged
Conversation
Install helm v3 and v4 side-by-side so OCP 5.0 users have both versions available during the v3 -> v4 migration. Both are downloaded from the OpenShift mirror (FIPS-compliant builds) and installed as explicit `helm3` and `helm4` binaries; the bare `helm` command is symlinked to v4, which is the default as of OCP 5.0. - tooling_versions.env: pin HELM3_VER=3.22.0-90 and HELM4_VER=4.3.0 - get-sources.sh: download both versions from their tarballs and verify checksums; record both in rh-manifest.txt - Dockerfile: symlink `helm` -> helm4 and generate bash completion for helm, helm3 and helm4 - get-tooling-versions.sh: report helm3 and helm4 in the installed-tools banner - README.md: document that both versions ship and `helm` defaults to v4 WTO-475 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Collaborator
|
I tested this PR and it seems to be working as expected ✔️
|
Fail with a clear message if helm4 is missing (e.g. an old container-root tarball reused without ./build.sh -u), instead of a confusing symlink error. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dkwon17
approved these changes
Oct 29, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
Adds helm v3 and v4 side-by-side to the Web Terminal tooling image, for WTO-475.
helm3andhelm4binaries.helmcommand is symlinked to v4, which is the default as of OCP 5.0.helmhelm3helm4This targets WTO 1.18.0 / OCP 5.0, where v4 becomes the default while v3 is still supported. The
helm3/helm4names stay stable across upgrades, so the only transition later (OCP 5.2, when v3 is dropped) is removinghelm3.Changes
tooling_versions.env: pinHELM3_VER=3.22.0-90andHELM4_VER=4.3.0get-sources.sh: download both versions from their mirror tarballs, verify checksums, install ashelm3/helm4; record both inrh-manifest.txtDockerfile: symlinkhelm→helm4; generate bash completion forhelm,helm3,helm4etc/get-tooling-versions.sh: reporthelm3andhelm4in the installed-tools bannerREADME.md: document both versions and thehelm→ v4 defaultTesting
Built locally with
./build.shand smoke-tested in the image:helm version→v4.3.0,helm3 version→v3.22.0+90.el9,helm4 version→v4.3.0helmsymlink →/usr/local/bin/helm4helm3andhelm4Notes / follow-ups
rh-manifest.txthas some pre-existing drift (stale kubectl version, oc URL trailing slash) unrelated to helm; left untouched here to keep this PR focused.🤖 Generated with Claude Code