Merge pull request #40532 from mickeyboxell/merged-main-dev-1.27

Merged main dev 1.27

Author: k8s-ci-robot

Makefile

@@ -9,7 +9,9 @@ CONTAINER_ENGINE ?= docker
 IMAGE_REGISTRY ?= gcr.io/k8s-staging-sig-docs
 IMAGE_VERSION=$(shell scripts/hash-files.sh Dockerfile Makefile | cut -c 1-12)
 CONTAINER_IMAGE   = $(IMAGE_REGISTRY)/k8s-website-hugo:v$(HUGO_VERSION)-$(IMAGE_VERSION)
-CONTAINER_RUN     = "$(CONTAINER_ENGINE)" run --rm --interactive --tty --volume "$(CURDIR):/src"
+# Mount read-only to allow use with tools like Podman in SELinux mode
+# Container targets don't need to write into /src
+CONTAINER_RUN     = "$(CONTAINER_ENGINE)" run --rm --interactive --tty --volume "$(CURDIR):/src:ro,Z"
 
 CCRED=\033[0;31m
 CCEND=\033[0m

content/de/docs/contribute/localization.md

@@ -111,7 +111,7 @@ mkdir content/de
 
 ### Lokalisierungs README Datei hinzufügen
 
-Um andere Lokalisierungsmitwirkende anzuleiten, füge eine neue [`README-**.md`](https://help.github.com/articles/about-readmes/) auf der obersten Ebene von k/website hinzu, wobei `**` der aus zwei Buchstaben bestehende Sprachcode ist. Eine deutsche README-Datei wäre zum Beispiel `README-de.md`.
+Um andere Lokalisierungsmitwirkende anzuleiten, füge eine neue [`README-**.md`](https://help.github.com/articles/about-readmes/) auf der obersten Ebene von kubernetes/website hinzu, wobei `**` der aus zwei Buchstaben bestehende Sprachcode ist. Eine deutsche README-Datei wäre zum Beispiel `README-de.md`.
 
 Gebe den Lokalisierungsmitwirkende in der lokalisierten `README-**.md`-Datei Anleitung zum Mitwirken. Füge dieselben Informationen ein, die auch in `README.md` enthalten sind, sowie:
 
@@ -262,7 +262,7 @@ In einem Entwicklungszweig zusammenzuarbeiten:
 
     `dev-<Quellversion>-<Sprachcode>.<Team-Meilenstein>`
 
-    Beispielsweise öffnet ein Genehmigender in einem deutschen Lokalisierungsteam den Entwicklungszweig `dev-1.12-de.1` direkt gegen das k/website-Repository, basierend auf dem Quellzweig für Kubernetes v1.12.
+    Beispielsweise öffnet ein Genehmigender in einem deutschen Lokalisierungsteam den Entwicklungszweig `dev-1.12-de.1` direkt gegen das kubernetes/website-Repository, basierend auf dem Quellzweig für Kubernetes v1.12.
 
 2. Einzelne Mitwirkende öffnen Feature-Zweige, die auf dem Entwicklungszweig basieren.
 

content/en/blog/_posts/2019-12-02-gardener-project-update.md

@@ -47,7 +47,7 @@ The essential idea is that so-called **seed** clusters are used to host the
 control planes of end-user clusters (botanically named **shoots**). \
 Gardener provides vanilla Kubernetes clusters as a service independent of the
 underlying infrastructure provider in a homogenous way, utilizing the upstream
-provided `k8s.gcr.io/*` images as open distribution. The project is built
+provided `k8s.gcr.io/*` images as open distribution _(update: `k8s.gcr.io` has been deprecated in favor of `registry.k8s.io`)._ The project is built
 entirely on top of Kubernetes extension concepts, and as such adds a custom API
 server, a controller-manager, and a scheduler to create and manage the lifecycle
 of Kubernetes clusters. It extends the Kubernetes API with custom resources,

content/en/blog/_posts/2021-04-13-kube-state-metrics-goes-v-2-0.md

@@ -35,7 +35,7 @@ So without further ado, here is the list of more noteworthy user-facing breaking
 * Metric labels that relate to Kubernetes were converted to snake_case.
 * If you are importing kube-state-metrics as a library, we have updated our go module path to `k8s.io/kube-state-metrics/v2`
 * All deprecated stable metrics were removed as per the [notice in the v1.9 release](https://github.com/kubernetes/kube-state-metrics/tree/release-1.9/docs#metrics-deprecation).
-* `quay.io/coreos/kube-state-metrics` images will no longer be updated. `k8s.gcr.io/kube-state-metrics/kube-state-metrics` is the new canonical location.
+* `quay.io/coreos/kube-state-metrics` images will no longer be updated. `k8s.gcr.io/kube-state-metrics/kube-state-metrics` is the new canonical location _(update: `k8s.gcr.io` has been deprecated in favor of `registry.k8s.io`)._
 * The helm chart that is part of the kubernetes/kube-state-metrics repository is deprecated. https://github.com/prometheus-community/helm-charts will be its new location. 
 
 For the full list of v2.0 release changes includes features, bug fixes and other breaking changes see the full [CHANGELOG](https://github.com/kubernetes/kube-state-metrics/blob/master/CHANGELOG.md).

content/en/blog/_posts/2023-01-05-retroactive-default-storage-class.md

@@ -1,6 +1,6 @@
 ---
 layout: blog
-title: "Kubernetes 1.26: Retroactive Default StorageClass"
+title: "Kubernetes v1.26: Retroactive Default StorageClass"
 date: 2023-01-05
 slug: retroactive-default-storage-class
 ---
@@ -11,7 +11,7 @@ The v1.25 release of Kubernetes introduced an alpha feature to change how a defa
 StorageClass was assigned to a PersistentVolumeClaim (PVC). With the feature enabled,
 you no longer need to create a default StorageClass first and PVC second to assign the
 class. Additionally, any PVCs without a StorageClass assigned can be updated later.
-This feature was graduated to beta in Kubernetes 1.26.
+This feature was graduated to beta in Kubernetes v1.26.
 
 You can read [retroactive default StorageClass assignment](/docs/concepts/storage/persistent-volumes/#retroactive-default-storageclass-assignment)
 in the Kubernetes documentation for more details about how to use that,
@@ -146,23 +146,35 @@ If you would like to see the feature in action and verify it works fine in your
    The PVC won't provision or bind (unless there is an existing, suitable PV already present)
    and will remain in <code>Pending</code> state.
 
+   ```shell
+   kubectl get pvc
    ```
-   $ kc get pvc
+
+   The output is similar to this:
+   ```console
    NAME      STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
    pvc-1     Pending   
    ```
 
 3. Configure one StorageClass as default.
 
+   ```shell
+   kubectl patch sc -p '{"metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
    ```
-   $ kc patch sc -p '{"metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
+
+   The output is similar to this:
+   ```console
    storageclass.storage.k8s.io/my-storageclass patched
    ```
 
 4. Verify that PersistentVolumeClaims is now provisioned correctly and was updated retroactively with new default StorageClass.
 
+   ```shell
+   kubectl get pvc
    ```
-   $ kc get pvc
+
+   The output is similar to this:
+   ```console
    NAME      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
    pvc-1     Bound    pvc-06a964ca-f997-4780-8627-b5c3bf5a87d8   1Gi        RWO            my-storageclass   87m
    ```