From 5250d4bacd21db7016a7f0cfbc26c9c8335cf9bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Doktor?= Date: Fri, 23 Jan 2026 14:58:18 +0100 Subject: [PATCH] ci.ocp: Use 0.0.0-dev tagged helm chart MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit in CI we are testing the latest kata-deploy, which requires the latest helm chart. The previous query doesn't work anymore, but these days we should be able to rely on the "0.0.0-dev" tag and on helm to print the to-be-installed version into console. Signed-off-by: Lukáš Doktor --- ci/openshift-ci/cluster/install_kata.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ci/openshift-ci/cluster/install_kata.sh b/ci/openshift-ci/cluster/install_kata.sh index 1ada2d813c..928445e553 100755 --- a/ci/openshift-ci/cluster/install_kata.sh +++ b/ci/openshift-ci/cluster/install_kata.sh @@ -51,13 +51,13 @@ apply_kata_deploy() { oc label --overwrite ns kube-system pod-security.kubernetes.io/enforce=privileged pod-security.kubernetes.io/warn=baseline pod-security.kubernetes.io/audit=baseline local version chart - version=$(curl -sSL https://api.github.com/repos/kata-containers/kata-containers/releases/latest | jq .tag_name | tr -d '"') + version='0.0.0-dev' chart="oci://ghcr.io/kata-containers/kata-deploy-charts/kata-deploy" # Ensure any potential leftover is cleaned up ... and this secret usually is not in case of previous failures oc delete secret sh.helm.release.v1.kata-deploy.v1 -n kube-system || true - echo "Installing kata using helm ${chart} ${version}" + echo "Installing kata using helm ${chart} ${version} (sha printed in helm output)" helm install kata-deploy --wait --namespace kube-system --set "image.reference=${KATA_DEPLOY_IMAGE%%:*},image.tag=${KATA_DEPLOY_IMAGE##*:}" "${chart}" --version "${version}" }