e2e: use official CentOS container location

registry.centos.org is not officially maintained by the CentOS
infrastructure team. The container images on quay.io are the official
once and we should use those instead.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
(cherry picked from commit e0ac70f8fba5a93d0759b054af4aae10ed98cb7b)

e2e/utils.go

@@ -254,7 +254,7 @@ func validateNormalUserPVCAccess(pvcPath string, f *framework.Framework) error {
 			Containers: []v1.Container{
 				{
 					Name:    "write-pod",
-					Image:   "registry.centos.org/centos:latest",
+					Image:   "quay.io/centos/centos:latest",
 					Command: []string{"/bin/sleep", "999999"},
 					SecurityContext: &v1.SecurityContext{
 						RunAsUser: &user,

examples/rbd/block-pod-clone.yaml

@@ -6,7 +6,7 @@ metadata:
 spec:
   containers:
     - name: centos
-      image: registry.centos.org/centos:latest
+      image: quay.io/centos/centos:latest
       command: ["/bin/sleep", "infinity"]
       volumeDevices:
         - name: data

examples/rbd/raw-block-pod.yaml

@@ -6,7 +6,7 @@ metadata:
 spec:
   containers:
     - name: centos
-      image: registry.centos.org/centos:latest
+      image: quay.io/centos/centos:latest
       command: ["/bin/sleep", "infinity"]
       volumeDevices:
         - name: data