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

Author: Tim Bannister

content/ja/docs/concepts/configuration/manage-resources-containers.md

@@ -601,7 +601,7 @@ Conditions:
 Events:
  FirstSeen LastSeen Count From SubobjectPath Reason Message
  Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {scheduler } scheduled Successfully assigned simmemleak-hra99 to kubernetes-node-tf0f
- Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "k8s.gcr.io/pause:0.8.0" already present on machine
+ Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "registry.k8s.io/pause:0.8.0" already present on machine
  Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD created Created with docker id 6a41280f516d
  Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD started Started with docker id 6a41280f516d
  Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} spec.containers{simmemleak} created Created with docker id 87348f12526a

content/ja/docs/concepts/configuration/secret.md

@@ -779,7 +779,7 @@ metadata:
 spec:
  containers:
  - name: test-container
- image: k8s.gcr.io/busybox
+ image: registry.k8s.io/busybox
  command: [ "/bin/sh", "-c", "env" ]
  envFrom:
  - secretRef:
@@ -994,7 +994,7 @@ spec:
  secretName: dotfile-secret
  containers:
  - name: dotfile-test-container
- image: k8s.gcr.io/busybox
+ image: registry.k8s.io/busybox
  command:
  - ls
  - "-l"

content/ja/docs/concepts/overview/working-with-objects/labels.md

@@ -130,7 +130,7 @@ metadata:
 spec:
  containers:
  - name: cuda-test
- image: "k8s.gcr.io/cuda-vector-add:v0.1"
+ image: "registry.k8s.io/cuda-vector-add:v0.1"
  resources:
  limits:
  nvidia.com/gpu: 1

content/ja/docs/concepts/storage/persistent-volumes.md

@@ -154,7 +154,7 @@ spec:
  path: /any/path/it/will/be/replaced
  containers:
  - name: pv-recycler
- image: "k8s.gcr.io/busybox"
+ image: "registry.k8s.io/busybox"
  command: ["/bin/sh", "-c", "test -e /scrub && rm -rf /scrub/..?* /scrub/.[!.]* /scrub/* && test -z \"$(ls -A /scrub)\" || exit 1"]
  volumeMounts:
  - name: vol

content/ja/docs/concepts/storage/volumes.md

@@ -76,7 +76,7 @@ metadata:
  name: test-ebs
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /test-ebs
@@ -163,7 +163,7 @@ metadata:
  name: test-cinder
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-cinder-container
  volumeMounts:
  - mountPath: /test-cinder
@@ -274,7 +274,7 @@ metadata:
  name: test-pd
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /cache
@@ -349,7 +349,7 @@ metadata:
  name: test-pd
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /test-pd
@@ -507,7 +507,7 @@ metadata:
  name: test-pd
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /test-pd
@@ -536,7 +536,7 @@ metadata:
 spec:
  containers:
  - name: test-webserver
- image: k8s.gcr.io/test-webserver:latest
+ image: registry.k8s.io/test-webserver:latest
  volumeMounts:
  - mountPath: /var/local/aaa
  name: mydir
@@ -666,7 +666,7 @@ metadata:
  name: test-portworx-volume-pod
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /mnt
@@ -848,7 +848,7 @@ metadata:
  name: test-vmdk
 spec:
  containers:
- - image: k8s.gcr.io/test-webserver
+ - image: registry.k8s.io/test-webserver
  name: test-container
  volumeMounts:
  - mountPath: /test-vmdk

content/ja/docs/concepts/workloads/controllers/statefulset.md

@@ -72,7 +72,7 @@ spec:
  terminationGracePeriodSeconds: 10
  containers:
  - name: nginx
- image: k8s.gcr.io/nginx-slim:0.8
+ image: registry.k8s.io/nginx-slim:0.8
  ports:
  - containerPort: 80
  name: web

content/ja/docs/reference/kubectl/cheatsheet.md

@@ -359,8 +359,8 @@ kubectl api-resources --api-group=extensions # "extensions" APIグループの
 # クラスター内で実行中のすべてのイメージ名を表示する
 kubectl get pods -A -o=custom-columns='DATA:spec.containers[*].image'
 
-# "k8s.gcr.io/coredns:1.6.2"を除いたすべてのイメージ名を表示する
-kubectl get pods -A -o=custom-columns='DATA:spec.containers[?(@.image!="k8s.gcr.io/coredns:1.6.2")].image'
+# "registry.k8s.io/coredns:1.6.2"を除いたすべてのイメージ名を表示する
+kubectl get pods -A -o=custom-columns='DATA:spec.containers[?(@.image!="registry.k8s.io/coredns:1.6.2")].image'
 
 # 名前に関係なくmetadata以下のすべてのフィールドを表示する
 kubectl get pods -A -o=custom-columns='DATA:metadata.*'

content/ja/docs/setup/learning-environment/minikube.md

@@ -54,7 +54,7 @@ MinikubeのサポートするKubernetesの機能:
  単純なHTTPサーバーである`echoserver`という既存のイメージを使用して、Kubernetes Deploymentを作りましょう。そして`--port`を使用して8080番ポートで公開しましょう。
 
  ```shell
- kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10
+ kubectl create deployment hello-minikube --image=registry.k8s.io/echoserver:1.10
  ```
 
  出力はこのようになります:

content/ja/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md

@@ -30,7 +30,7 @@ when using kubeadm to set up a kubernetes cluster.
  document assumes these default ports. However, they are configurable through
  the kubeadm config file.
 * Each host must [have docker, kubelet, and kubeadm installed](/ja/docs/setup/production-environment/tools/kubeadm/install-kubeadm/).
-* Each host should have access to the Kubernetes container image registry (`k8s.gcr.io`) or list/pull the required etcd image using `kubeadm config images list/pull`. This guide will setup etcd instances as [static pods](/docs/tasks/configure-pod-container/static-pod/) managed by a kubelet.
+* Each host should have access to the Kubernetes container image registry (`registry.k8s.io`) or list/pull the required etcd image using `kubeadm config images list/pull`. This guide will setup etcd instances as [static pods](/docs/tasks/configure-pod-container/static-pod/) managed by a kubelet.
 * Some infrastructure to copy files between hosts. For example `ssh` and `scp`
  can satisfy this requirement.
 
@@ -251,7 +251,7 @@ this example.
  ```sh
  docker run --rm -it \
  --net host \
- -v /etc/kubernetes:/etc/kubernetes k8s.gcr.io/etcd:${ETCD_TAG} etcdctl \
+ -v /etc/kubernetes:/etc/kubernetes registry.k8s.io/etcd:${ETCD_TAG} etcdctl \
  --cert /etc/kubernetes/pki/etcd/peer.crt \
  --key /etc/kubernetes/pki/etcd/peer.key \
  --cacert /etc/kubernetes/pki/etcd/ca.crt \

content/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

@@ -36,7 +36,7 @@ Readiness Probeによるチェックを無効にし、これらがアプリケ
 長期間実行されているアプリケーションの多くは、再起動されるまで回復できないような異常な状態になることがあります。
 Kubernetesはこのような状況を検知し、回復するためのLiveness Probeを提供します。
 
-この演習では、`k8s.gcr.io/busybox`イメージのコンテナを起動するPodを作成します。
+この演習では、`registry.k8s.io/busybox`イメージのコンテナを起動するPodを作成します。
 Podの構成ファイルは次の通りです。
 
 {{< codenew file="pods/probe/exec-liveness.yaml" >}}
@@ -76,8 +76,8 @@ kubectl describe pod liveness-exec
 FirstSeen LastSeen Count From SubobjectPath Type Reason Message
 --------- -------- ----- ---- ------------- -------- ------ -------
 24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
-23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox"
-23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "k8s.gcr.io/busybox"
+23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "registry.k8s.io/busybox"
+23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "registry.k8s.io/busybox"
 23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
 23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
 ```
@@ -94,8 +94,8 @@ kubectl describe pod liveness-exec
 FirstSeen LastSeen Count From SubobjectPath Type Reason Message
 --------- -------- ----- ---- ------------- -------- ------ -------
 37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
-36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox"
-36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "k8s.gcr.io/busybox"
+36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "registry.k8s.io/busybox"
+36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "registry.k8s.io/busybox"
 36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
 36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
 2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
@@ -117,7 +117,7 @@ liveness-exec 1/1 Running 1 1m
 ## HTTPリクエストによるLiveness Probeを定義する {#define-a-liveness-http-request}
 
 別の種類のLiveness Probeでは、HTTP GETリクエストを使用します。
-次の構成ファイルは、`k8s.gcr.io/liveness`イメージを使用したコンテナを起動するPodを作成します。
+次の構成ファイルは、`registry.k8s.io/liveness`イメージを使用したコンテナを起動するPodを作成します。
 
 {{< codenew file="pods/probe/http-liveness.yaml" >}}