From 0d74d403e672a38052c20b04dcd90a17051142f1 Mon Sep 17 00:00:00 2001 From: FedericoFeresini <65897118+FedericoFeresini@users.noreply.github.com> Date: Tue, 13 Feb 2024 15:37:01 +0100 Subject: [PATCH] chore(cluster-scanner): bump cluster-scanner to 0.5.9 (#1613) --- charts/cluster-scanner/Chart.yaml | 2 +- charts/cluster-scanner/README.md | 12 ++++++------ charts/cluster-scanner/values.yaml | 4 ++-- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/charts/cluster-scanner/Chart.yaml b/charts/cluster-scanner/Chart.yaml index f87193a82..35016813a 100644 --- a/charts/cluster-scanner/Chart.yaml +++ b/charts/cluster-scanner/Chart.yaml @@ -3,7 +3,7 @@ name: cluster-scanner description: Sysdig Cluster Scanner type: application -version: 0.9.0 +version: 0.9.1 appVersion: "0.1.0" home: https://www.sysdig.com/ diff --git a/charts/cluster-scanner/README.md b/charts/cluster-scanner/README.md index 1f8e5990a..1f577f6e5 100644 --- a/charts/cluster-scanner/README.md +++ b/charts/cluster-scanner/README.md @@ -25,7 +25,7 @@ $ pre-commit run -a $ helm repo add sysdig https://charts.sysdig.com $ helm repo update $ helm upgrade --install sysdig-cluster-scanner sysdig/cluster-scanner \ - --create-namespace -n sysdig --version=0.9.0 \ + --create-namespace -n sysdig --version=0.9.1 \ --set global.clusterConfig.name=CLUSTER_NAME \ --set global.sysdig.region=SYSDIG_REGION \ --set global.sysdig.accessKey=YOUR-KEY-HERE @@ -55,7 +55,7 @@ To install the chart with the release name `cluster-scanner`, run: ```console $ helm upgrade --install sysdig-cluster-scanner sysdig/cluster-scanner \ - --create-namespace -n sysdig --version=0.9.0 \ + --create-namespace -n sysdig --version=0.9.1 \ --set global.clusterConfig.name=CLUSTER_NAME \ --set global.sysdig.region=SYSDIG_REGION \ --set global.sysdig.accessKey=YOUR-KEY-HERE @@ -110,7 +110,7 @@ The following table lists the configurable parameters of the `cluster-scanner` c | sslVerifyRegistryCertificate | Can be set to false to allow insecure connections registries, Such as for registries with self-signed or private certificates. By default, certificates are always verified. | true | | runtimeStatusIntegrator.image.registry | The image registry to use for the Runtime Status Integrator component of Cluster Scanner | quay.io | | runtimeStatusIntegrator.image.repository | The image repository to use for pulling the Runtime Status Integrator image | sysdig/runtime-status-integrator | -| runtimeStatusIntegrator.image.tag | | "0.5.4" | +| runtimeStatusIntegrator.image.tag | | "0.5.9" | | runtimeStatusIntegrator.multiCluster | When the Cluster Scanner is running in `multi` mode, set the secret name to be used to retrieve the kubeconfig configuration to connect to the clusters to inspect. | | | runtimeStatusIntegrator.localCluster | Restrict access to specific Docker secrets when Cluster Scanner is running in `local` mode. The default behavior is listing all secrets. See `values.yaml` for an example. Optional. | | | runtimeStatusIntegrator.ports.metrics | The port to be used to expose prometheus metrics for the Runtime Status Integrator | 25000 | @@ -123,7 +123,7 @@ The following table lists the configurable parameters of the `cluster-scanner` c | runtimeStatusIntegrator.natsJS.user | The username to be used in the NATS JetStream instance the Runtime Status Integrator is going to start | "default-user" | | imageSbomExtractor.image.registry | The image registry to use for the Image SBOM Extractor component of Cluster Scanner | quay.io | | imageSbomExtractor.image.repository | The image repository to use for pulling the Image SBOM Extractor image | sysdig/image-sbom-extractor | -| imageSbomExtractor.image.tag | | "0.5.4" | +| imageSbomExtractor.image.tag | | "0.5.9" | | imageSbomExtractor.ports.metrics | The port to be used to expose prometheus metrics for the Image SBOM Extractor | 25001 | | imageSbomExtractor.ports.probes | The port to be used for healthcheck probes for the Image SBOM Extractor | 7001 | | imageSbomExtractor.resources.limits.cpu | Image SBOM Extractor CPU limit per replica | "1" | @@ -163,7 +163,7 @@ Specify each parameter using the **`--set key=value[,key=value]`** argument to ` ```console $ helm upgrade --install sysdig-cluster-scanner sysdig/cluster-scanner \ - --create-namespace -n sysdig --version=0.9.0 \ + --create-namespace -n sysdig --version=0.9.1 \ --set global.sysdig.region="us1" ``` @@ -172,7 +172,7 @@ installing the chart. For example: ```console $ helm upgrade --install sysdig-cluster-scanner sysdig/cluster-scanner \ - --create-namespace -n sysdig --version=0.9.0 \ + --create-namespace -n sysdig --version=0.9.1 \ --values values.yaml ``` diff --git a/charts/cluster-scanner/values.yaml b/charts/cluster-scanner/values.yaml index 0d6b391b7..02228fa84 100644 --- a/charts/cluster-scanner/values.yaml +++ b/charts/cluster-scanner/values.yaml @@ -108,7 +108,7 @@ runtimeStatusIntegrator: # The image repository to use for pulling the Runtime Status Integrator # image repository: sysdig/runtime-status-integrator - tag: "0.5.4" + tag: "0.5.9" # Params to manage leader election # Leader election is implemented leveraging the native capabilities of # Kubernetes see: https://kubernetes.io/blog/2016/01/simple-leader-election-with-kubernetes/ @@ -170,7 +170,7 @@ imageSbomExtractor: registry: quay.io # The image repository to use for pulling the Image SBOM Extractor image repository: sysdig/image-sbom-extractor - tag: "0.5.4" + tag: "0.5.9" ports: # The port to be used to expose prometheus metrics for the Image SBOM # Extractor