Update Registry location after gcr Driver/Syncer images were removed

aws-samples · Oct 14, 2024 · eb7ee15 · eb7ee15
1 parent 3a69399
commit eb7ee15
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/eks-anywhere-vsphere/Addons/Core/storage-driver/vmware-csi/vsphere-csi-driver.yaml b/eks-anywhere-vsphere/Addons/Core/storage-driver/vmware-csi/vsphere-csi-driver.yaml
@@ -281,7 +281,7 @@ spec:
             - mountPath: /csi
               name: socket-dir
         - name: vsphere-csi-controller
-          image: gcr.io/cloud-provider-vsphere/csi/release/driver:v3.0.0
+          image: registry.k8s.io/csi-vsphere/driver:v3.3.0
           args:
             - "--fss-name=internal-feature-states.csi.vsphere.vmware.com"
             - "--fss-namespace=$(CSI_NAMESPACE)"
@@ -337,7 +337,7 @@ spec:
             - name: socket-dir
               mountPath: /csi
         - name: vsphere-syncer
-          image: gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.0.0
+          image: registry.k8s.io/csi-vsphere/syncer:v3.3.0
           args:
             - "--leader-election"
             - "--leader-election-lease-duration=120s"