From 6a0fc644757524968f097dc97d8fa24d5c5dccdd Mon Sep 17 00:00:00 2001 From: Andrei Kvapil Date: Tue, 22 Apr 2025 19:12:44 +0200 Subject: [PATCH] Update LINSTOR to v1.31.0 Signed-off-by: Andrei Kvapil --- .../charts/piraeus/Chart.yaml | 4 +-- .../charts/piraeus/templates/config.yaml | 27 +++++++++---------- 2 files changed, 15 insertions(+), 16 deletions(-) diff --git a/packages/system/piraeus-operator/charts/piraeus/Chart.yaml b/packages/system/piraeus-operator/charts/piraeus/Chart.yaml index 0a2b853d..598dff4c 100644 --- a/packages/system/piraeus-operator/charts/piraeus/Chart.yaml +++ b/packages/system/piraeus-operator/charts/piraeus/Chart.yaml @@ -3,8 +3,8 @@ name: piraeus description: | The Piraeus Operator manages software defined storage clusters using LINSTOR in Kubernetes. type: application -version: 2.7.1 -appVersion: "v2.7.1" +version: 2.8.1 +appVersion: "v2.8.1" maintainers: - name: Piraeus Datastore url: https://piraeus.io diff --git a/packages/system/piraeus-operator/charts/piraeus/templates/config.yaml b/packages/system/piraeus-operator/charts/piraeus/templates/config.yaml index ca17da64..f912c1f3 100644 --- a/packages/system/piraeus-operator/charts/piraeus/templates/config.yaml +++ b/packages/system/piraeus-operator/charts/piraeus/templates/config.yaml @@ -17,20 +17,19 @@ data: # quay.io/piraeusdatastore/piraeus-server:v1.24.2 components: linstor-controller: - tag: v1.29.2 + tag: v1.31.0 image: piraeus-server linstor-satellite: - # Pin with digest to ensure we pull the version with downgraded thin-send-recv - tag: v1.29.2 + tag: v1.31.0 image: piraeus-server linstor-csi: - tag: v1.6.4 + tag: v1.7.1 image: piraeus-csi drbd-reactor: - tag: v1.6.0 + tag: v1.8.0 image: drbd-reactor ha-controller: - tag: v1.2.3 + tag: v1.3.0 image: piraeus-ha-controller drbd-shutdown-guard: tag: v1.0.0 @@ -39,7 +38,7 @@ data: tag: v0.11 image: ktls-utils drbd-module-loader: - tag: v9.2.12 + tag: v9.2.13 # The special "match" attribute is used to select an image based on the node's reported OS. # The operator will first check the k8s node's ".status.nodeInfo.osImage" field, and compare it against the list # here. If one matches, that specific image name will be used instead of the fallback image. @@ -90,25 +89,25 @@ data: base: registry.k8s.io/sig-storage components: csi-attacher: - tag: v4.7.0 + tag: v4.8.1 image: csi-attacher csi-livenessprobe: - tag: v2.14.0 + tag: v2.15.0 image: livenessprobe csi-provisioner: - tag: v5.1.0 + tag: v5.2.0 image: csi-provisioner csi-snapshotter: - tag: v8.1.0 + tag: v8.2.1 image: csi-snapshotter csi-resizer: - tag: v1.12.0 + tag: v1.13.2 image: csi-resizer csi-external-health-monitor-controller: - tag: v0.13.0 + tag: v0.14.0 image: csi-external-health-monitor-controller csi-node-driver-registrar: - tag: v2.12.0 + tag: v2.13.0 image: csi-node-driver-registrar {{- range $idx, $value := .Values.imageConfigOverride }} {{ add $idx 1 }}_helm_override.yaml: |