Merge remote-tracking branch 'upstream/main' into update-docs-reference-kubectl-cheatsheet-md

Author: utkarsh-singh1

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

README-zh.md

@@ -22,11 +22,11 @@ This repository contains the assets required to build the [Kubernetes website an
 <!--
 ## Using this repository
 
-You can run the website locally using Hugo (Extended version), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
+You can run the website locally using [Hugo (Extended version)](https://gohugo.io/), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
 -->
 ## 使用这个仓库
 
-可以使用 Hugo（扩展版）在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
+可以使用 [Hugo（扩展版）](https://gohugo.io/)在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
 
 <!--
 ## Prerequisites
@@ -150,11 +150,11 @@ This will start the local Hugo server on port 1313. Open up your browser to <htt
 ## 构建 API 参考页面
 
 <!--
-The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.
+The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, also known as OpenAPI specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.
 
 To update the reference pages for a new Kubernetes release follow these steps:
 -->
-位于 `content/en/docs/reference/kubernetes-api` 的 API 参考页面是根据 Swagger 规范构建的，使用 <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>。
+位于 `content/en/docs/reference/kubernetes-api` 的 API 参考页面是使用 <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs> 根据 Swagger 规范（也称为 OpenAPI 规范）构建的。
 
 要更新 Kubernetes 新版本的参考页面，请执行以下步骤：
 

api-ref-assets/api/swagger.json

@@ -99,6 +99,7 @@
     - initContainerStatuses
     - containerStatuses
     - ephemeralContainerStatuses
+    - resize
 
 - definition: io.k8s.api.core.v1.Container
   field_categories:
@@ -127,6 +128,7 @@
   - name: Resources
     fields:
     - resources
+    - resizePolicy
   - name: Lifecycle
     fields:
     - lifecycle
@@ -219,6 +221,9 @@
     fields:
     - volumeMounts
     - volumeDevices
+  - name: Resources
+    fields:
+    - resizePolicy
   - name: Lifecycle
     fields:
     - terminationMessagePath

api-ref-assets/config/fields.yaml

@@ -66,18 +66,18 @@ parts:
   - name: PriorityClass
     group: scheduling.k8s.io
     version: v1
-  - name: PodScheduling
+  - name: PodSchedulingContext
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClaim
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClaimTemplate
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClass
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
 - name: Service Resources
   chapters:
   - name: Service
@@ -148,6 +148,12 @@ parts:
   - name: CertificateSigningRequest
     group: certificates.k8s.io
     version: v1
+  - name: ClusterTrustBundle
+    group: certificates.k8s.io
+    version: v1alpha1
+  - name: SelfSubjectReview
+    group: authentication.k8s.io
+    version: v1beta1
 - name: Authorization Resources
   chapters:
   - name: LocalSubjectAccessReview
@@ -191,6 +197,9 @@ parts:
   - name: PodDisruptionBudget
     group: policy
     version: v1
+  - name: IPAddress
+    group: networking.k8s.io
+    version: v1alpha1
 - name: Extend Resources
   chapters:
   - name: CustomResourceDefinition

api-ref-assets/config/toc.yaml

@@ -102,6 +102,16 @@ main {
   }
 }
 
+::selection {
+  background: #326ce5;
+  color: white;
+}
+
+::-moz-selection {
+  background: #326ce5;
+  color: white;
+}
+
 // HEADER
 
 #hamburger {

assets/scss/_base.scss

@@ -0,0 +1,9 @@
+---
+title: Resourcen-Verwaltung für Pods und Container
+content_type: concept
+weight: 40
+feature:
+  title: Automatisches Bin Packing
+  description: >
+    Container können je nach Systemanforderungen auf spezifischen Nodes ausgeführt werden. Somit kann eine effiziente Nutzung von Ressourcen erreicht werden.
+---

content/de/docs/concepts/configuration/manage-resource-containers.md

@@ -0,0 +1,9 @@
+---
+title: Secrets
+content_type: concept
+feature:
+  title: Verwaltung von Secrets und Konfigurationen
+  description: >
+    Deploye und aktualisiere Secrets sowie Anwendungskonfigurationen, ohne ein Image neu zu bauen oder Secrets preiszugeben.
+weight: 30
+---

content/de/docs/concepts/configuration/secret.md

@@ -1,4 +1,8 @@
 ---
 title: "Kubernetes erweitern"
 weight: 110
+feature:
+  title: Für Erweiterungen entworfen
+  description: >
+    Kubernetes kann ohne Änderungen am Upstream-Quelltext erweitert werden.
 ---

content/de/docs/concepts/extend-kubernetes/_index.md

@@ -0,0 +1,18 @@
+---
+title: IPv4/IPv6 dual-stack
+description: >-
+  Kubernetes erlaubt Netzwerkkonfigurationen mit IPv4 oder IPv6 (Single Stack).
+  Im Dual-Stack-Betrieb kann IPv4 im Verbund mit IPv6 verwendet werden.
+
+feature:
+  title: IPv4/IPv6 Dual-Stack
+  description: >
+    Pods und Dienste können gleichzeitig IPv4- und IPv6-Adressen verwenden.
+content_type: concept
+reviewers:
+  - lachie83
+  - khenidak
+  - aramase
+  - bridgetkromhout
+weight: 90
+---