Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

registry change in docs (k8s.gcr.io -> registry.k8s.io) #38501

Merged
merged 5 commits into from
Jan 28, 2023
Merged

registry change in docs (k8s.gcr.io -> registry.k8s.io) #38501

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e966026
registry change in en docs
SergeyKanzhelev Jan 12, 2023
96bdbad
Update content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md
SergeyKanzhelev Jan 20, 2023
ace97d6
Update content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md
SergeyKanzhelev Jan 20, 2023
d0d5901
Update content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
SergeyKanzhelev Jan 20, 2023
e8d37ae
Update content/en/blog/_posts/2022-05-27-maxunavailable-for-statefuls…
SergeyKanzhelev Jan 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
git log -2
SergeyKanzhelev marked this conversation as resolved.
Show resolved Hide resolved
---
layout: blog
title: 'Kubernetes 1.14: Local Persistent Volumes GA'
Expand Down Expand Up @@ -129,7 +130,7 @@ spec:
spec:
containers:
- name: test-container
image: k8s.gcr.io/busybox
image: registry.k8s.io/busybox
SergeyKanzhelev marked this conversation as resolved.
Show resolved Hide resolved
command:
- "/bin/sh"
args:
Expand Down
2 changes: 1 addition & 1 deletion ...og/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ The team has made progress in the last few months that is well worth celebrating

- The K8s-Infrastructure Working Group released an automated billing report that they start every meeting off by reviewing as a group.
- DNS for k8s.io and kubernetes.io are also fully [community-owned](https://groups.google.com/g/kubernetes-dev/c/LZTYJorGh7c/m/u-ydk-yNEgAJ), with community members able to [file issues](https://github.com/kubernetes/k8s.io/issues/new?assignees=&labels=wg%2Fk8s-infra&template=dns-request.md&title=DNS+REQUEST%3A+%3Cyour-dns-record%3E) to manage records.
- The container registry [k8s.gcr.io](https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io) is also fully community-owned and available for all Kubernetes subprojects to use.
- The container registry [registry.k8s.io](https://github.com/kubernetes/k8s.io/tree/main/registry.k8s.io) is also fully community-owned and available for all Kubernetes subprojects to use.
_Note:_ The container registry has changed to registry.k8s.io. Updated on August 25, 2022.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@celanthe FYI

- The Kubernetes [publishing-bot](https://github.com/kubernetes/publishing-bot) responsible for keeping k8s.io/kubernetes/staging repositories published to their own top-level repos (For example: [kubernetes/api](https://github.com/kubernetes/api)) runs on a community-owned cluster.
- The gcsweb.k8s.io service used to provide anonymous access to GCS buckets for kubernetes artifacts runs on a community-owned cluster.
Expand Down
2 changes: 1 addition & 1 deletion content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ metadata:
spec:
containers:
- name: agnhost
image: k8s.gcr.io/e2e-test-images/agnhost:2.35
image: registry.k8s.io/e2e-test-images/agnhost:2.35
SergeyKanzhelev marked this conversation as resolved.
Show resolved Hide resolved
command: ["/agnhost", "grpc-health-checking"]
ports:
- containerPort: 5000
Expand Down
4 changes: 2 additions & 2 deletions content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ spec:
app: nginx
spec:
containers:
- image: k8s.gcr.io/nginx-slim:0.8
- image: registry.k8s.io/nginx-slim:0.8
SergeyKanzhelev marked this conversation as resolved.
Show resolved Hide resolved
imagePullPolicy: IfNotPresent
name: nginx
updateStrategy:
Expand All @@ -66,7 +66,7 @@ If you enable the new feature and you don't specify a value for `maxUnavailable`
I'll run through a scenario based on that example manifest to demonstrate how this feature works. I will deploy a StatefulSet that
has 5 replicas, with `maxUnavailable` set to 2 and `partition` set to 0.

I can trigger a rolling update by changing the image to `k8s.gcr.io/nginx-slim:0.9`. Once I initiate the rolling update, I can
I can trigger a rolling update by changing the image to `registry.k8s.io/nginx-slim:0.9`. Once I initiate the rolling update, I can
watch the pods update 2 at a time as the current value of maxUnavailable is 2. The below output shows a span of time and is not
complete. The maxUnavailable can be an absolute number (for example, 2) or a percentage of desired Pods (for example, 10%). The
absolute number is calculated from percentage by rounding up to the nearest integer.
Expand Down