Merge pull request #124 from asa3311/update-k8s.gcr.io-to-registry.k8s.io

Replace k8s.gcr.io references with registry.k8s.io

Author: k8s-ci-robot

charts/nfs-server-provisioner/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v1
 appVersion: 4.0.8
 description: nfs-server-provisioner is an out-of-tree dynamic provisioner for Kubernetes. You can use it to quickly & easily deploy shared storage that works almost anywhere.
 name: nfs-server-provisioner
-version: 1.7.0
+version: 1.8.0
 maintainers:
 - name: kiall
   email: [email protected]

charts/nfs-server-provisioner/README.md

@@ -57,7 +57,7 @@ their default values.
 |:-------------------------------|:----------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------|
 | `extraArgs` | [Additional command line arguments](https://github.com/kubernetes-incubator/external-storage/blob/HEAD/nfs/docs/deployment.md#arguments) | `{}`
 | `imagePullSecrets`             | Specify image pull secrets                                                                                      | `nil` (does not add image pull secrets to deployed pods) |
-| `image.repository`             | The image repository to pull from                                                                               | `k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8`         |
+| `image.repository`             | The image repository to pull from                                                                               | `registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8`         |
 | `image.tag`                    | The image tag to pull                                                                                           | `v4.0.8`                                                 |
 | `image.digest`                 | The image digest to pull, this option has precedence over `image.tag`                                           | `nil`                                                    |
 | `image.pullPolicy`             | Image pull policy                                                                                               | `IfNotPresent`                                           |

charts/nfs-server-provisioner/values.yaml

@@ -7,7 +7,7 @@ replicaCount: 1
 # imagePullSecrets:
 
 image:
-  repository: k8s.gcr.io/sig-storage/nfs-provisioner
+  repository: registry.k8s.io/sig-storage/nfs-provisioner
   tag: v4.0.8
   # digest:
   pullPolicy: IfNotPresent

deploy/kubernetes/deployment.yaml

@@ -63,7 +63,7 @@ spec:
       serviceAccount: nfs-provisioner
       containers:
         - name: nfs-provisioner
-          image: k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8
+          image: registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8
           ports:
             - name: nfs
               containerPort: 2049

deploy/kubernetes/pod.yaml

@@ -11,7 +11,7 @@ spec:
   serviceAccount: nfs-provisioner
   containers:
     - name: nfs-provisioner
-      image: k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8
+      image: registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8
       ports:
         - name: nfs
           containerPort: 2049

deploy/kubernetes/statefulset.yaml

@@ -63,7 +63,7 @@ spec:
       terminationGracePeriodSeconds: 10
       containers:
         - name: nfs-provisioner
-          image: k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8
+          image: registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8
           ports:
             - name: nfs
               containerPort: 2049

docs/deployment.md

@@ -29,7 +29,7 @@ $ make container
 If you are running in Kubernetes, it will pull the image from GCR for you. Or you can do it yourself.
 
 ```
-$ docker pull k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8
+$ docker pull registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8
 ```
 
 ## Deploying the provisioner
@@ -87,15 +87,15 @@ You may want to specify the hostname the NFS server exports from, i.e. the serve
 $ docker run --cap-add DAC_READ_SEARCH --cap-add SYS_RESOURCE \
 --security-opt seccomp:deploy/docker/nfs-provisioner-seccomp.json \
 -v $HOME/.kube:/.kube:Z \
-k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8 \
+registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8 \
 -provisioner=example.com/nfs \
 -kubeconfig=/.kube/config
 ```
 or
 ```
 $ docker run --cap-add DAC_READ_SEARCH --cap-add SYS_RESOURCE \
 --security-opt seccomp:deploy/docker/nfs-provisioner-seccomp.json \
-k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8 \
+registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8 \
 -provisioner=example.com/nfs \
 -master=http://172.17.0.1:8080
 ```
@@ -110,7 +110,7 @@ With the two above options, the run command will look something like this.
 $ docker run --privileged \
 -v $HOME/.kube:/.kube:Z \
 -v /xfs:/export:Z \
-k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8 \
+registry.k8s.io/sig-storage/nfs-provisioner:v4.0.8 \
 -provisioner=example.com/nfs \
 -kubeconfig=/.kube/config \
 -enable-xfs-quota=true

release-tools/SIDECAR_RELEASE_PROCESS.md

@@ -88,9 +88,9 @@ naming convention `<hostpath-deployment-version>-on-<kubernetes-version>`.
 1. If release was a new major/minor version, create a new `release-<minor>`
    branch at that commit.
 1. Check [image build status](https://k8s-testgrid.appspot.com/sig-storage-image-build).
-1. Promote images from k8s-staging-sig-storage to k8s.gcr.io/sig-storage. From
+1. Promote images from k8s-staging-sig-storage to registry.k8s.io/sig-storage. From
    the [k8s image
-   repo](https://github.com/kubernetes/k8s.io/tree/HEAD/k8s.gcr.io/images/k8s-staging-sig-storage),
+   repo](https://github.com/kubernetes/k8s.io/tree/HEAD/registry.k8s.io/images/k8s-staging-sig-storage),
    run `./generate.sh > images.yaml`, and send a PR with the updated images.
    Once merged, the image promoter will copy the images from staging to prod.
 1. Update [kubernetes-csi/docs](https://github.com/kubernetes-csi/docs) sidecar

release-tools/cloudbuild.yaml

@@ -13,7 +13,7 @@
 # See https://github.com/kubernetes/test-infra/blob/HEAD/config/jobs/image-pushing/README.md
 # for more details on image pushing process in Kubernetes.
 #
-# To promote release images, see https://github.com/kubernetes/k8s.io/tree/HEAD/k8s.gcr.io/images/k8s-staging-sig-storage.
+# To promote release images, see https://github.com/kubernetes/k8s.io/tree/HEAD/registry.k8s.io/images/k8s-staging-sig-storage.
 
 # This must be specified in seconds. If omitted, defaults to 600s (10 mins).
 # Building the Dockerfile we maintain for non-amd64 architectures has been found

release-tools/prow.sh

@@ -813,7 +813,7 @@ install_snapshot_controller() {
           modified="$(cat "$i" | while IFS= read -r line; do
               nocomments="$(echo "$line" | sed -e 's/ *#.*$//')"
               if echo "$nocomments" | grep -q '^[[:space:]]*image:[[:space:]]*'; then
-                  # Split 'image: k8s.gcr.io/sig-storage/snapshot-controller:v3.0.0'
+                  # Split 'image: registry.k8s.io/sig-storage/snapshot-controller:v3.0.0'
                   # into image (snapshot-controller:v3.0.0),
                   # name (snapshot-controller),
                   # tag (v3.0.0).
@@ -914,11 +914,11 @@ patch_kubernetes () {
     local source="$1" target="$2"
 
     if [ "${CSI_PROW_DRIVER_CANARY}" = "canary" ]; then
-        # We cannot replace k8s.gcr.io/sig-storage with gcr.io/k8s-staging-sig-storage because
+        # We cannot replace registry.k8s.io/sig-storage with gcr.io/k8s-staging-sig-storage because
         # e2e.test does not support it (see test/utils/image/manifest.go). Instead we
         # invoke the e2e.test binary with KUBE_TEST_REPO_LIST set to a file that
         # overrides that registry.
-        find "$source/test/e2e/testing-manifests/storage-csi/mock" -name '*.yaml' -print0 | xargs -0 sed -i -e 's;k8s.gcr.io/sig-storage/\(.*\):v.*;k8s.gcr.io/sig-storage/\1:canary;'
+        find "$source/test/e2e/testing-manifests/storage-csi/mock" -name '*.yaml' -print0 | xargs -0 sed -i -e 's;registry.k8s.io/sig-storage/\(.*\):v.*;registry.k8s.io/sig-storage/\1:canary;'
         cat >"$target/e2e-repo-list" <<EOF
 sigStorageRegistry: gcr.io/k8s-staging-sig-storage
 EOF