changed k8s.gcr.io to registry.k8s.io (#8667)

This commit is contained in:
Long Wu Yuan 2022-06-10 16:31:52 +05:30 committed by GitHub
parent 2852e2998c
commit 96b6228a6b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
73 changed files with 180 additions and 5165 deletions

View file

@ -24,7 +24,7 @@ spec:
spec:
containers:
- name: ingress-nginx-controller
image: k8s.gcr.io/ingress-nginx/controller:v1.0.4@sha256:545cff00370f28363dad31e3b59a94ba377854d3a11f18988f5f9e56841ef9ef
image: registry.k8s.io/ingress-nginx/controller:v1.0.4@sha256:545cff00370f28363dad31e3b59a94ba377854d3a11f18988f5f9e56841ef9ef
args: ...
```
@ -33,7 +33,7 @@ The easiest way to do this is e.g. (do note you may need to change the name para
```
kubectl set image deployment/ingress-nginx-controller \
controller=k8s.gcr.io/ingress-nginx/controller:v1.0.5@sha256:55a1fcda5b7657c372515fe402c3e39ad93aa59f6e4378e82acd99912fe6028d \
controller=registry.k8s.io/ingress-nginx/controller:v1.0.5@sha256:55a1fcda5b7657c372515fe402c3e39ad93aa59f6e4378e82acd99912fe6028d \
-n ingress-nginx
```

View file

@ -17,7 +17,7 @@ spec:
spec:
containers:
- name: nginxhello
image: k8s.gcr.io/e2e-test-images/echoserver:2.3
image: registry.k8s.io/e2e-test-images/echoserver:2.3
ports:
- containerPort: 8080
env:

View file

@ -3,7 +3,7 @@ controller:
defaultBackend:
enabled: true
image:
registry: k8s.gcr.io
registry: registry.k8s.io
image: ingress-nginx/nginx-errors
tag: "0.48.1"
extraVolumes:

View file

@ -36,7 +36,7 @@ spec:
spec:
containers:
- name: nginx-error-server
image: k8s.gcr.io/ingress-nginx/nginx-errors:0.49.0
image: registry.k8s.io/ingress-nginx/nginx-errors:0.49.0
ports:
- containerPort: 8080
# Setting the environment variable DEBUG we can see the headers sent

View file

@ -14,7 +14,7 @@ spec:
spec:
containers:
- name: http-svc
image: k8s.gcr.io/e2e-test-images/echoserver:2.3
image: registry.k8s.io/e2e-test-images/echoserver:2.3
ports:
- containerPort: 8080
env:

View file

@ -70,7 +70,7 @@ spec:
spec:
containers:
- name: http-svc
image: k8s.gcr.io/e2e-test-images/echoserver:2.3
image: registry.k8s.io/e2e-test-images/echoserver:2.3
ports:
- containerPort: 8080
env:

View file

@ -24,7 +24,7 @@ spec:
# hostNetwork: true
terminationGracePeriodSeconds: 60
containers:
- image: k8s.gcr.io/ingress-nginx/controller:v1.0.5
- image: registry.k8s.io/ingress-nginx/controller:v1.0.5
name: controller
readinessProbe:
httpGet:

View file

@ -256,7 +256,7 @@ Note: The below is based on the nginx [documentation](https://docs.nginx.com/ngi
```console
$ docker ps | grep ingress-nginx-controller
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d9e1d243156a k8s.gcr.io/ingress-nginx/controller "/usr/bin/dumb-init …" 19 minutes ago Up 19 minutes k8s_ingress-nginx-controller_ingress-nginx-controller-67956bf89d-mqxzt_kube-system_079f31ec-aa37-11e8-ad39-080027a227db_0
d9e1d243156a registry.k8s.io/ingress-nginx/controller "/usr/bin/dumb-init …" 19 minutes ago Up 19 minutes k8s_ingress-nginx-controller_ingress-nginx-controller-67956bf89d-mqxzt_kube-system_079f31ec-aa37-11e8-ad39-080027a227db_0
```
3. Exec into the container

View file

@ -173,7 +173,7 @@ In the Zipkin interface we can see the details:
3. Apply a basic Service and Ingress Resource:
```
# Create Echoheaders Deployment
$ kubectl run echoheaders --image=k8s.gcr.io/echoserver:1.4 --replicas=1 --port=8080
$ kubectl run echoheaders --image=registry.k8s.io/echoserver:1.4 --replicas=1 --port=8080
# Expose as a Cluster-IP
$ kubectl expose deployment echoheaders --port=80 --target-port=8080 --name=echoheaders-x