Skip to content

Commit

Permalink
feat(cluster-scanner): bump cluster-scanner to 0.5.4 (#1580)
Browse files Browse the repository at this point in the history
  • Loading branch information
@michele-mangili
michele-mangili authored Jan 29, 2024
1 parent cd9d871 commit d1c37ca
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion charts/cluster-scanner/Chart.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: cluster-scanner
description: Sysdig Cluster Scanner

type: application
version: 0.8.7
version: 0.8.8
appVersion: "0.1.0"
home: https://www.sysdig.com/

Expand Down
12 changes: 6 additions & 6 deletions charts/cluster-scanner/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.8.7 \
--create-namespace -n sysdig --version=0.8.8 \
--set global.clusterConfig.name=CLUSTER_NAME \
--set global.sysdig.region=SYSDIG_REGION \
--set global.sysdig.accessKey=YOUR-KEY-HERE
Expand Down Expand Up @@ -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.8.7 \
--create-namespace -n sysdig --version=0.8.8 \
--set global.clusterConfig.name=CLUSTER_NAME \
--set global.sysdig.region=SYSDIG_REGION \
--set global.sysdig.accessKey=YOUR-KEY-HERE
Expand Down Expand Up @@ -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. | <code>true</code> |
| runtimeStatusIntegrator.image.registry | The image registry to use for the Runtime Status Integrator component of Cluster Scanner | <code>quay.io</code> |
| runtimeStatusIntegrator.image.repository | The image repository to use for pulling the Runtime Status Integrator image | <code>sysdig/runtime-status-integrator</code> |
| runtimeStatusIntegrator.image.tag | | <code>"0.5.3"</code> |
| runtimeStatusIntegrator.image.tag | | <code>"0.5.4"</code> |
| 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. | <code></code> |
| 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. | <code></code> |
| runtimeStatusIntegrator.ports.metrics | The port to be used to expose prometheus metrics for the Runtime Status Integrator | <code>25000</code> |
Expand All @@ -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 | <code>"default-user"</code> |
| imageSbomExtractor.image.registry | The image registry to use for the Image SBOM Extractor component of Cluster Scanner | <code>quay.io</code> |
| imageSbomExtractor.image.repository | The image repository to use for pulling the Image SBOM Extractor image | <code>sysdig/image-sbom-extractor</code> |
| imageSbomExtractor.image.tag | | <code>"0.5.3"</code> |
| imageSbomExtractor.image.tag | | <code>"0.5.4"</code> |
| imageSbomExtractor.ports.metrics | The port to be used to expose prometheus metrics for the Image SBOM Extractor | <code>25001</code> |
| imageSbomExtractor.ports.probes | The port to be used for healthcheck probes for the Image SBOM Extractor | <code>7001</code> |
| imageSbomExtractor.resources.limits.cpu | Image SBOM Extractor CPU limit per replica | <code>"1"</code> |
Expand Down Expand Up @@ -162,7 +162,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.8.7 \
--create-namespace -n sysdig --version=0.8.8 \
--set global.sysdig.region="us1"
```

Expand All @@ -171,7 +171,7 @@ installing the chart. For example:

```console
$ helm upgrade --install sysdig-cluster-scanner sysdig/cluster-scanner \
--create-namespace -n sysdig --version=0.8.7 \
--create-namespace -n sysdig --version=0.8.8 \
--values values.yaml
```

Expand Down
4 changes: 2 additions & 2 deletions charts/cluster-scanner/values.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.3"
tag: "0.5.4"
# 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/
Expand Down Expand Up @@ -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.3"
tag: "0.5.4"
ports:
# The port to be used to expose prometheus metrics for the Image SBOM
# Extractor
Expand Down

0 comments on commit d1c37ca

Please sign in to comment.