kubernetes
/
examples
mirror of https://github.com/kubernetes/examples.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: move registry from k8s.gcr.io to registry.k8s.io

This commit is contained in:
ajayk 2022-11-30 03:01:20 +00:00
parent 8c357b6f7d
commit 33dfad21f4
35 changed files with 45 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
guestbook-go/README.md
View File

@ -109,7 +109,7 @@ The Redis master we created earlier is a single pod (REPLICAS = 1), while the Re
$ kubectl get rc
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
redis-master redis-master redis app=redis,role=master 1
redis-replica redis-replica k8s.gcr.io/redis-slave:v2 app=redis,role=replica 2
redis-replica redis-replica registry.k8s.io/redis-slave:v2 app=redis,role=replica 2
...
```
@ -178,9 +178,9 @@ This is a simple Go `net/http` ([negroni](https://github.com/codegangsta/negroni
```console
$ kubectl get rc
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
guestbook guestbook k8s.gcr.io/guestbook:v3 app=guestbook 3
guestbook guestbook registry.k8s.io/guestbook:v3 app=guestbook 3
redis-master redis-master redis app=redis,role=master 1
redis-replica redis-replica k8s.gcr.io/redis-replica:v2 app=redis,role=replica 2
redis-replica redis-replica registry.k8s.io/redis-replica:v2 app=redis,role=replica 2
...
```

2
guestbook-go/guestbook-controller.json
View File

@ -22,7 +22,7 @@
"containers":[
{
"name":"guestbook",
"image":"k8s.gcr.io/guestbook:v3",
"image":"registry.k8s.io/guestbook:v3",
"ports":[
{
"name":"http-server",

2
guestbook-go/redis-master-controller.json
View File

@ -25,7 +25,7 @@
"containers":[
{
"name":"redis-master",
"image":"k8s.gcr.io/redis:e2e",
"image":"registry.k8s.io/redis:e2e",
"ports":[
{
"name":"redis-server",

2
guestbook-go/redis-replica-controller.json
View File

@ -25,7 +25,7 @@
"containers":[
{
"name":"redis-replica",
"image":"k8s.gcr.io/redis-slave:v2",
"image":"registry.k8s.io/redis-slave:v2",
"ports":[
{
"name":"redis-server",

2
guestbook/all-in-one/guestbook-all-in-one.yaml
View File

@ -35,7 +35,7 @@ spec:
spec:
containers:
- name: master
image: k8s.gcr.io/redis:e2e # or just image: redis
image: registry.k8s.io/redis:e2e # or just image: redis
resources:
requests:
cpu: 100m

2
guestbook/legacy/redis-master-controller.yaml
View File

@ -17,7 +17,7 @@ spec:
spec:
containers:
- name: master
image: k8s.gcr.io/redis:e2e # or just image: redis
image: registry.k8s.io/redis:e2e # or just image: redis
resources:
requests:
cpu: 100m

2
guestbook/redis-master-deployment.yaml
View File

@ -18,7 +18,7 @@ spec:
spec:
containers:
- name: master
image: k8s.gcr.io/redis:e2e # or just image: redis
image: registry.k8s.io/redis:e2e # or just image: redis
resources:
requests:
cpu: 100m

2
staging/cluster-dns/dns-backend-rc.yaml
View File

@ -15,7 +15,7 @@ spec:
spec:
containers:
- name: dns-backend
image: k8s.gcr.io/example-dns-backend:v1
image: registry.k8s.io/example-dns-backend:v1
ports:
- name: backend-port
containerPort: 8000

2
staging/cluster-dns/dns-frontend-pod.yaml
View File

@ -7,7 +7,7 @@ metadata:
spec:
containers:
- name: dns-frontend
image: k8s.gcr.io/example-dns-frontend:v1
image: registry.k8s.io/example-dns-frontend:v1
command:
- python
- client.py

2
staging/explorer/README.md
View File

@ -2,7 +2,7 @@
Explorer is a little container for examining the runtime environment Kubernetes produces for your pods.
The intended use is to substitute k8s.gcr.io/explorer for your intended container, and then visit it via the proxy.
The intended use is to substitute registry.k8s.io/explorer for your intended container, and then visit it via the proxy.
Currently, you can look at:
* The environment variables to make sure Kubernetes is doing what you expect.

2
staging/explorer/pod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: explorer
image: k8s.gcr.io/explorer:1.0
image: registry.k8s.io/explorer:1.0
args: ["-port=8080"]
ports:
- containerPort: 8080

2
staging/spark/spark-gluster/spark-master-controller.yaml
View File

@ -16,7 +16,7 @@ spec:
spec:
containers:
- name: spark-master
image: k8s.gcr.io/spark:1.5.2_v1
image: registry.k8s.io/spark:1.5.2_v1
command: ["/start-master"]
ports:
- containerPort: 7077

2
staging/spark/spark-gluster/spark-worker-controller.yaml
View File

@ -17,7 +17,7 @@ spec:
spec:
containers:
- name: spark-worker
image: k8s.gcr.io/spark:1.5.2_v1
image: registry.k8s.io/spark:1.5.2_v1
command: ["/start-worker"]
ports:
- containerPort: 8888

2
staging/spark/spark-master-controller.yaml
View File

@ -13,7 +13,7 @@ spec:
spec:
containers:
- name: spark-master
image: k8s.gcr.io/spark:1.5.2_v1
image: registry.k8s.io/spark:1.5.2_v1
command: ["/start-master"]
ports:
- containerPort: 7077

2
staging/spark/spark-worker-controller.yaml
View File

@ -13,7 +13,7 @@ spec:
spec:
containers:
- name: spark-worker
image: k8s.gcr.io/spark:1.5.2_v1
image: registry.k8s.io/spark:1.5.2_v1
command: ["/start-worker"]
ports:
- containerPort: 8081

2
staging/spark/zeppelin-controller.yaml
View File

@ -13,7 +13,7 @@ spec:
spec:
containers:
- name: zeppelin
image: k8s.gcr.io/zeppelin:v0.5.6_v1
image: registry.k8s.io/zeppelin:v0.5.6_v1
ports:
- containerPort: 8080
resources:

2
staging/storage/redis/redis-controller.yaml
View File

@ -14,7 +14,7 @@ spec:
spec:
containers:
- name: redis
image: k8s.gcr.io/redis:v1
image: registry.k8s.io/redis:v1
ports:
- containerPort: 6379
resources:

4
staging/storage/redis/redis-master.yaml
View File

@ -9,7 +9,7 @@ metadata:
spec:
containers:
- name: master
image: k8s.gcr.io/redis:v1
image: registry.k8s.io/redis:v1
env:
- name: MASTER
value: "true"
@ -22,7 +22,7 @@ spec:
- mountPath: /redis-master-data
name: data
- name: sentinel
image: k8s.gcr.io/redis:v1
image: registry.k8s.io/redis:v1
env:
- name: SENTINEL
value: "true"

2
staging/storage/redis/redis-sentinel-controller.yaml
View File

@ -15,7 +15,7 @@ spec:
spec:
containers:
- name: sentinel
image: k8s.gcr.io/redis:v1
image: registry.k8s.io/redis:v1
env:
- name: SENTINEL
value: "true"

2
staging/storage/rethinkdb/admin-pod.yaml
View File

@ -7,7 +7,7 @@ metadata:
name: rethinkdb-admin
spec:
containers:
- image: k8s.gcr.io/rethinkdb:1.16.0_1
- image: registry.k8s.io/rethinkdb:1.16.0_1
name: rethinkdb
env:
- name: POD_NAMESPACE

2
staging/storage/rethinkdb/rc.yaml
View File

@ -16,7 +16,7 @@ spec:
role: replicas
spec:
containers:
- image: k8s.gcr.io/rethinkdb:1.16.0_1
- image: registry.k8s.io/rethinkdb:1.16.0_1
name: rethinkdb
env:
- name: POD_NAMESPACE

2
staging/volumes/nfs/nfs-server-deployment.yaml
View File

@ -14,7 +14,7 @@ spec:
spec:
containers:
- name: nfs-server
image: k8s.gcr.io/volume-nfs:0.8
image: registry.k8s.io/volume-nfs:0.8
ports:
- name: nfs
containerPort: 2049

6
staging/volumes/portworx/README.md
View File

@ -45,7 +45,7 @@ The following examples assumes that you already have a running Kubernetes cluste
name: test-portworx-volume-pod
spec:
containers:
- image: k8s.gcr.io/test-webserver
- image: registry.k8s.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-portworx-volume
@ -181,7 +181,7 @@ The following examples assumes that you already have a running Kubernetes cluste
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-portworx-volume
@ -338,7 +338,7 @@ create Portworx volumes out of band and they will be created automatically.
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-portworx-volume

2
staging/volumes/portworx/portworx-volume-pod.yaml
View File

@ -4,7 +4,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: /test-portworx-volume

2
staging/volumes/portworx/portworx-volume-pvcpod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-portworx-volume

2
staging/volumes/portworx/portworx-volume-pvcscpod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-portworx-volume

4
staging/volumes/scaleio/README.md
View File

@ -84,7 +84,7 @@ metadata:
name: pod-0
spec:
containers:
- image: k8s.gcr.io/test-webserver
- image: registry.k8s.io/test-webserver
name: pod-0
volumeMounts:
- mountPath: /test-pd
@ -221,7 +221,7 @@ metadata:
spec:
containers:
- name: pod-sio-small-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- mountPath: /test
name: test-data

2
staging/volumes/scaleio/pod-sc-pvc.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: pod-sio-small-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- mountPath: /test
name: test-data

2
staging/volumes/scaleio/pod.yaml
View File

@ -4,7 +4,7 @@ metadata:
name: pod-0
spec:
containers:
- image: k8s.gcr.io/test-webserver
- image: registry.k8s.io/test-webserver
name: pod-0
volumeMounts:
- mountPath: /test-pd

10
staging/volumes/vsphere/README.md
View File

@ -38,7 +38,7 @@
name: test-vmdk
spec:
containers:
- image: k8s.gcr.io/test-webserver
- image: registry.k8s.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-vmdk
@ -180,7 +180,7 @@
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-vmdk
@ -350,7 +350,7 @@
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-vmdk
@ -568,7 +568,7 @@
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test
@ -653,7 +653,7 @@ vSphere volumes can be consumed by Stateful Sets.
spec:
containers:
- name: nginx
image: k8s.gcr.io/nginx-slim:0.8
image: registry.k8s.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web

2
staging/volumes/vsphere/simple-statefulset.yaml
View File

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

2
staging/volumes/vsphere/vsphere-volume-pod.yaml
View File

@ -4,7 +4,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

2
staging/volumes/vsphere/vsphere-volume-pvcpod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-vmdk

2
staging/volumes/vsphere/vsphere-volume-pvcscpod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test-vmdk

2
staging/volumes/vsphere/vsphere-volume-pvcscvsanpod.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
image: k8s.gcr.io/test-webserver
image: registry.k8s.io/test-webserver
volumeMounts:
- name: test-volume
mountPath: /test