Merge branch 'kubernetes:main' into main

Author: divya-mohan0209

OWNERS

@@ -11,6 +11,7 @@ emeritus_approvers:
 # - chenopis, commented out to disable PR assignments
 # - irvifa, commented out to disable PR assignments
 # - jaredbhatti, commented out to disable PR assignments
+# - jimangel, commented out to disable PR assignments
 # - kbarnard10, commented out to disable PR assignments
 # - steveperry-53, commented out to disable PR assignments
 - stewart-yu

README-ja.md

@@ -16,7 +16,7 @@ Hugo(Extended version)を使用してWebサイトをローカルで実行する
 このリポジトリを使用するには、以下をローカルにインストールする必要があります。
 
 - [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
+- [Go](https://go.dev/)
 - [Hugo(Extended version)](https://gohugo.io/)
 - [Docker](https://www.docker.com/)などのコンテナランタイム
 

content/en/blog/_posts/2022-12-13-host-process-containers-ga/index.md

@@ -54,7 +54,7 @@ closed and the storage will be unmounted.
 
 HostProcess and Linux privileged containers enable similar scenarios but differ
 greatly in their implementation (hence the naming difference). HostProcess containers
-have their own [PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#windowssecuritycontextoptions-v1-core) fields.
+have their own [PodSecurityContext](/docs/reference/generated/kubernetes-api/v1.25/#windowssecuritycontextoptions-v1-core) fields.
 Those used to configure Linux privileged containers **do not** apply. Enabling privileged access to a Windows host is a
 fundamentally different process than with Linux so the configuration and
 capabilities of each differ significantly. Below is a diagram detailing the
@@ -110,7 +110,7 @@ Please note that within a Pod, you can't mix HostProcess containers with normal
 
 - Work through [Create a Windows HostProcess Pod](/docs/tasks/configure-pod-container/create-hostprocess-pod/)
 
-- Read about Kubernetes [Pod Security Standards](/docs/concepts/security/pod-security-standards/) and [Pod Security Admission](docs/concepts/security/pod-security-admission/)
+- Read about Kubernetes [Pod Security Standards](/docs/concepts/security/pod-security-standards/) and [Pod Security Admission](/docs/concepts/security/pod-security-admission/)
 
 - Read the enhancement proposal [Windows Privileged Containers and Host Networking Mode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/1981-windows-privileged-container-support) (KEP-1981)
 

content/en/blog/_posts/2022-12-20-validating-admission-policies-alpha/index.md

@@ -60,12 +60,14 @@ kind: ValidatingAdmissionPolicyBinding
 metadata:
   name: "demo-binding-test.example.com"
 spec:
-  policy: "demo-policy.example.com"
+  policyName: "demo-policy.example.com"
   matchResources:
     namespaceSelector:
-    - key: environment,
-      operator: In,
-      values: ["test"]
+      matchExpressions:
+      - key: environment
+        operator: In
+        values:
+        - test
 ```
 
 This `ValidatingAdmissionPolicyBinding` resource binds the above policy only to
@@ -115,14 +117,16 @@ kind: ValidatingAdmissionPolicyBinding
 metadata:
   name: "demo-binding-production.example.com"
 spec:
-  policy: "demo-policy.example.com"
-  paramsRef:
+  policyName: "demo-policy.example.com"
+  paramRef:
     name: "demo-params-production.example.com"
   matchResources:
     namespaceSelector:
-    - key: environment,
-      operator: In,
-      values: ["production"]
+      matchExpressions:
+      - key: environment
+        operator: In
+        values:
+        - production
 ```
 
 ```yaml

content/en/docs/concepts/overview/working-with-objects/namespaces.md

@@ -147,7 +147,7 @@ kubectl api-resources --namespaced=false
 
 ## Automatic labelling
 
-{{< feature-state state="beta" for_k8s_version="1.21" >}}
+{{< feature-state for_k8s_version="1.22" state="stable" >}}
 
 The Kubernetes control plane sets an immutable {{< glossary_tooltip text="label" term_id="label" >}}
 `kubernetes.io/metadata.name` on all namespaces, provided that the `NamespaceDefaultLabelName`

content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md

@@ -26,22 +26,7 @@ criteria that Pod should be satisfied before considered schedulable. This field
 only when a Pod is created (either by the client, or mutated during admission). After creation,
 each schedulingGate can be removed in arbitrary order, but addition of a new scheduling gate is disallowed.
 
-{{<mermaid>}}
-stateDiagram-v2
-    s1: pod created
-    s2: pod scheduling gated
-    s3: pod scheduling ready
-    s4: pod running
-    if: empty scheduling gates?
-    [*] --> s1
-    s1 --> if
-    s2 --> if: scheduling gate removed
-    if --> s2: no
-    if --> s3: yes  
-    s3 --> s4
-    s4 --> [*]
-{{< /mermaid >}}
-
+{{< figure src="/docs/images/podSchedulingGates.svg" alt="pod-scheduling-gates-diagram" caption="Figure. Pod SchedulingGates" class="diagram-large" link="https://mermaid.live/edit#pako:eNplkktTwyAUhf8KgzuHWpukaYszutGlK3caFxQuCVMCGSDVTKf_XfKyPlhxz4HDB9wT5lYAptgHFuBRsdKxenFMClMYFIdfUdRYgbiD6ItJTEbR8wpEq5UpUfnDTf-5cbPoJjcbXdcaE61RVJIiqJvQ_Y30D-OCt-t3tFjcR5wZayiVnIGmkv4NiEfX9jijKTmmRH5jf0sRugOP0HyHUc1m6KGMFP27cM28fwSJDluPpNKaXqVJzmFNfHD2APRKSjnNFx9KhIpmzSfhVls3eHdTRrwG8QnxKfEZUUNeYTDBNbiaKRF_5dSfX-BQQQ0FpnEqQLJWhwIX5hyXsjbYl85wTINrgeC2EZd_xFQy7b_VJ6GCdd-itkxALE84dE3fAqXyIUZya6Qqe711OspVCI2ny2Vv35QqVO3-htt66ZWomAvVcZcv8yTfsiSFfJOydZoKvl_ttjLJVlJsblcJw-czwQ0zr9ZeqGDgeR77b2jD8xdtjtDn" >}}
 ## Usage example
 
 To mark a Pod not-ready for scheduling, you can create it with one or more scheduling gates like this:

content/en/docs/contribute/advanced.md

@@ -190,3 +190,7 @@ When you're ready to start the recording, click Record to Cloud.
 When you're ready to stop recording, click Stop.
 
 The video uploads automatically to YouTube.
+
+### Offboarding a SIG Co-chair (Emeritus)
+
+See: [k/community/sig-docs/offboarding.md](https://github.com/kubernetes/community/blob/master/sig-docs/offboarding.md)

content/en/docs/images/podSchedulingGates.svg

@@ -193,9 +193,10 @@ spec:
   matchResources:
     namespaceSelector:
       matchExpressions:
-      - key: environment,
-        operator: NotIn,
-        values: ["test"]
+      - key: environment
+        operator: NotIn
+        values:
+        - test
 ```
 
 And have a parameter resource like:
@@ -222,7 +223,7 @@ spec:
   matchResources:
     namespaceSelector:
       matchExpressions:
-      - key: environment,
+      - key: environment
         operator: Exists
 ```
 

content/en/docs/reference/access-authn-authz/validating-admission-policy.md

@@ -0,0 +1,23 @@
+---
+title: Feature gate
+id: feature-gate
+date: 2023-01-12
+full_link: /docs/reference/command-line-tools-reference/feature-gates/
+short_description: >
+  A way to control whether or not a particular Kubernetes feature is enabled.
+
+aka: 
+tags:
+- fundamental
+- operation
+---
+
+Feature gates are a set of keys (opaque string values) that you can use to control which
+Kubernetes features are enabled in your cluster.
+
+<!--more-->
+
+You can turn these features on or off using the `--feature-gates` command line flag on each Kubernetes component.
+Each Kubernetes component lets you enable or disable a set of feature gates that are relevant to that component.
+The Kubernetes documentation lists all current 
+[feature gates](/docs/reference/command-line-tools-reference/feature-gates/) and what they control.