Fix errors in integration tests

warm-metal · Mar 7, 2025 · a2fb0b1 · a2fb0b1
1 parent da2c075
commit a2fb0b1
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
diff --git a/.github/workflows/metrics.yaml b/.github/workflows/metrics.yaml
@@ -14,7 +14,7 @@ jobs:
         uses: helm/kind-action@v1.12.0
         with:
           cluster_name: kind-${{ github.run_id }}
-          kubectl_version: "v1.25.2"
+          kubectl_version: "v1.32.2"
           config: ./hack/ci/containerd-cluster-conf.yaml
       - name: Build image
         run: ./hack/ci/build.sh

diff --git a/README.md b/README.md
@@ -29,12 +29,12 @@ git remote set-head origin -a
 ```
 
 ### Migration of CSI driver
-In release `v2.0.0`, we are updating the CSI driver name from `container-image.warm-metal.tech` to `container-image.csi.k8s.io`. This change may cause disruptions to your existing workloads if the driver name is not updated.
+In release `v2.0.0`, we are updating the CSI driver name from `csi-image.warm-metal.tech` to `container-image.csi.k8s.io`. This change may cause disruptions to your existing workloads if the driver name is not updated.
 
 **To ensure a smooth transition:**
 1. **Install Both Versions**: To avoid any breaking changes, you can install both the old and new versions of the CSI driver simultaneously. Both versions are compatible and have been tested to work side-by-side, as verified in our integration tests.
 
-1. **Update Your Workloads**: Migrate your workloads to use the new driver name `container-image.warm-metal.tech`. This process will involve updating your storage class definitions and any other configurations that reference the old driver name.
+1. **Update Your Workloads**: Migrate your workloads to use the new driver name `container-image.csi.k8s.io`. This process will involve updating your storage class definitions and any other configurations that reference the old driver name.
 
 1. **Remove the Old Driver**: Once all workloads have been successfully migrated and verified with the new driver, you can safely remove the older version of the driver from your cluster.
 

diff --git a/test/integration/compatible-manifests/ephemeral-volume.yaml b/test/integration/compatible-manifests/ephemeral-volume.yaml
@@ -17,13 +17,13 @@ spec:
   volumes:
     - name: rw
       csi:
-        driver: container-image.csi.k8s.io
+        driver: csi-image.warm-metal.tech
         volumeAttributes:
           image: "docker.io/warmmetal/container-image-csi-driver-test:simple-fs"
           pullAlways: "true"
     - name: ro
       csi:
-        driver: container-image.csi.k8s.io
+        driver: csi-image.warm-metal.tech
         readOnly: true
         volumeAttributes:
           image: "docker.io/warmmetal/container-image-csi-driver-test:simple-fs"

diff --git a/test/integration/compatible-manifests/pre-provisioned-pv.yaml b/test/integration/compatible-manifests/pre-provisioned-pv.yaml
@@ -1,30 +1,30 @@
 kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
-  name: container-image.csi.k8s.io
-provisioner: container-image.csi.k8s.io
+  name: csi-image.warm-metal.tech
+provisioner: csi-image.warm-metal.tech
 ---
 apiVersion: v1
 kind: PersistentVolume
 metadata:
   name: compatible-pv-test-container-image-csi-driver-test-simple-fs
 spec:
-  storageClassName: container-image.csi.k8s.io
+  storageClassName: csi-image.warm-metal.tech
   capacity:
     storage: 5Gi
   accessModes:
     - ReadOnlyMany
   persistentVolumeReclaimPolicy: Retain
   csi:
-    driver: container-image.csi.k8s.io
+    driver: csi-image.warm-metal.tech
     volumeHandle: "docker.io/warmmetal/container-image-csi-driver-test:simple-fs"
 ---
 apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
   name: compatible-pvc-test-container-image-csi-driver-test-simple-fs
 spec:
-  storageClassName: container-image.csi.k8s.io
+  storageClassName: csi-image.warm-metal.tech
   accessModes:
     - ReadOnlyMany
   resources: