From a196ff230c44ec99b4bf2aa145abc741defc99b3 Mon Sep 17 00:00:00 2001 From: Marko Bevc Date: Mon, 2 Nov 2026 15:50:11 +0000 Subject: [PATCH] chore(helm): bump k8s-reporter chart to 2.8.0 with CLI v2.52.0 The chart still pinned the reporter image to CLI v2.36.1. Moving to v2.52.0 brings these reporter fixes: - a Running pod with an empty imageID no longer aborts the whole snapshot (#1195) - artifacts pulled by digest on containerd are named by image reference rather than a bare sha256 (#1204) - the image is built with Go 1.26.10, fixing CVE-2026-111943 (#1291) - the scratch image has a writable /tmp (#1105) The flags and config file format that the chart passes to snapshot k8s are unchanged, so templates and values need no changes. --- charts/k8s-reporter/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charts/k8s-reporter/Chart.yaml b/charts/k8s-reporter/Chart.yaml index 337ae4629..4736298a2 100644 --- a/charts/k8s-reporter/Chart.yaml +++ b/charts/k8s-reporter/Chart.yaml @@ -15,9 +15,9 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 2.7.0 +version: 2.8.0 # This is the version number of the (CLI) application being deployed. This version number should be # incremented each time you make changes to the application. They should reflect the version the # application is using. It is recommended to use it with quotes. -appVersion: "v2.36.1" +appVersion: "v2.52.0"