Skip to content

Commit 460aa90

Browse files
authored
Docs: Migrate to AR. (#12807)
1 parent 97bbec4 commit 460aa90

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

Diff for: MANUAL_RELEASE.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Promoting the images basically means that images, that were pushed to staging co
9393

9494
```
9595
...
96-
pushing manifest for gcr.io/k8s-staging-ingress-nginx/controller:v1.0.2@sha256:e15fac6e8474d77e1f017edc33d804ce72a184e3c0a30963b2a0d7f0b89f6b16
96+
pushing manifest for us-central1-docker.pkg.dev/k8s-staging-images/ingress-nginx/controller:v1.0.2@sha256:e15fac6e8474d77e1f017edc33d804ce72a184e3c0a30963b2a0d7f0b89f6b16
9797
...
9898
```
9999

@@ -113,7 +113,7 @@ Promoting the images basically means that images, that were pushed to staging co
113113

114114
- For making, it easier, you can edit your branch directly in the browser. But be careful about making any mistake.
115115

116-
- Insert the sha(s) & the tag(s), in a new line, in this file [Project kubernetes/k8s.io Ingress-Nginx-Controller Images](https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml) Look at this [example PR and the diff](https://github.com/kubernetes/k8s.io/pull/2536) to see how it was done before
116+
- Insert the sha(s) & the tag(s), in a new line, in this file [Project kubernetes/k8s.io Ingress-Nginx-Controller Images](https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-ingress-nginx/images.yaml) Look at this [example PR and the diff](https://github.com/kubernetes/k8s.io/pull/2536) to see how it was done before
117117

118118
- Save and commit
119119

Diff for: NEW_CONTRIBUTOR.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -325,9 +325,9 @@ minikube start
325325
🐳 Preparing Kubernetes v1.23.3 on Docker 20.10.12 ...
326326
▪ kubelet.housekeeping-interval=5m
327327
🔎 Verifying Kubernetes components...
328-
▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
329-
▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
330-
▪ Using image k8s.gcr.io/ingress-nginx/controller:v1.2.1
328+
▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.1.1
329+
▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.1.1
330+
▪ Using image registry.k8s.io/ingress-nginx/controller:v1.2.1
331331
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
332332
🔎 Verifying ingress addon...
333333
🌟 Enabled addons: ingress, storage-provisioner, default-storageclass

Diff for: ginkgo_upgrade.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Promoting the images basically means that images, that were pushed to staging co
4949

5050
```
5151
...
52-
pushing manifest for gcr.io/k8s-staging-ingress-nginx/controller:v1.0.2@sha256:e15fac6e8474d77e1f017edc33d804ce72a184e3c0a30963b2a0d7f0b89f6b16
52+
pushing manifest for us-central1-docker.pkg.dev/k8s-staging-images/ingress-nginx/controller:v1.0.2@sha256:e15fac6e8474d77e1f017edc33d804ce72a184e3c0a30963b2a0d7f0b89f6b16
5353
...
5454
```
5555

@@ -65,11 +65,11 @@ Promoting the images basically means that images, that were pushed to staging co
6565

6666
- Create a branch in your fork, named as the issue number for this release
6767

68-
- In the related branch, of your fork, edit the file k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml.
68+
- In the related branch, of your fork, edit the file registry.k8s.io/images/k8s-staging-ingress-nginx/images.yaml.
6969

7070
- For making it easier, you can edit your branch directly in the browser. But be careful about making any mistake.
7171

72-
- Insert the sha(s) & the tag(s), in a new line, in this file [Project kubernetes/k8s.io Ingress-Nginx-Controller Images](https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml) Look at this [example PR and the diff](https://github.com/kubernetes/k8s.io/pull/4499) to see how it was done before
72+
- Insert the sha(s) & the tag(s), in a new line, in this file [Project kubernetes/k8s.io Ingress-Nginx-Controller Images](https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-ingress-nginx/images.yaml) Look at this [example PR and the diff](https://github.com/kubernetes/k8s.io/pull/4499) to see how it was done before
7373

7474
- Save and commit
7575

@@ -128,4 +128,4 @@ Promoting the images basically means that images, that were pushed to staging co
128128

129129
- Finally merge the PR.
130130

131-
## END ##
131+
## END ##

0 commit comments

Comments
 (0)