Merge pull request #45049 from Vyom-Yadav/merged-main-dev-1.30

Merge main branch into dev-1.30

Author: k8s-ci-robot

content/en/docs/reference/kubectl/quick-reference.md

@@ -112,11 +112,11 @@ Kubernetes manifests can be defined in YAML or JSON. The file extension `.yaml`,
 `.yml`, and `.json` can be used.
 
 ```bash
-kubectl apply -f ./my-manifest.yaml            # create resource(s)
-kubectl apply -f ./my1.yaml -f ./my2.yaml      # create from multiple files
-kubectl apply -f ./dir                         # create resource(s) in all manifest files in dir
-kubectl apply -f https://git.io/vPieo          # create resource(s) from url
-kubectl create deployment nginx --image=nginx  # start a single instance of nginx
+kubectl apply -f ./my-manifest.yaml                 # create resource(s)
+kubectl apply -f ./my1.yaml -f ./my2.yaml           # create from multiple files
+kubectl apply -f ./dir                              # create resource(s) in all manifest files in dir
+kubectl apply -f https://example.com/manifest.yaml  # create resource(s) from url (Note: this is an example domain and does not contain a valid manifest)
+kubectl create deployment nginx --image=nginx       # start a single instance of nginx
 
 # create a Job which prints "Hello World"
 kubectl create job hello --image=busybox:1.28 -- echo "Hello World"

content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md

@@ -333,7 +333,10 @@ support [Network Policy](/docs/concepts/services-networking/network-policies/).
 See a list of add-ons that implement the
 [Kubernetes networking model](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-network-model).
 
-You can install a Pod network add-on with the following command on the
+
+Please refer to the [Installing Addons](/docs/concepts/cluster-administration/addons/#networking-and-network-policy)
+page for a non-exhaustive list of networking addons supported by Kubernetes. 
+You can install a Pod network add-on with the following command on the 
 control-plane node or a node that has the kubeconfig credentials:
 
 ```bash

content/ja/docs/concepts/architecture/_index.md

@@ -1,4 +1,8 @@
 ---
 title: "クラスターのアーキテクチャ"
 weight: 30
+description: >
+  Kubernetesの背後にあるアーキテクチャのコンセプト。
 ---
+
+{{< figure src="/images/docs/kubernetes-cluster-architecture.svg" alt="Components of Kubernetes" caption="Kubernetesクラスターのアーキテクチャ" class="diagram-large" >}}

content/ko/docs/reference/command-line-tools-reference/feature-gates-removed.md renamed to content/ko/docs/reference/command-line-tools-reference/feature-gates-removed/index.md

@@ -151,7 +151,7 @@ Kubernetes 默认提供访问权限并非是每个集群都需要的。
 It is vital to periodically review the Kubernetes RBAC settings for redundant entries and
 possible privilege escalations.
 If an attacker is able to create a user account with the same name as a deleted user,
-they can automatically inherit all the rights of the deleted user, especially the
+they can automatically inherit all the rights of the deleted user, specially the
 rights assigned to that user.
  -->
 ### 定期检查  {#periodic-review}
@@ -260,8 +260,8 @@ You should only allow access to create PersistentVolume objects for:
 你应该只允许以下实体具有创建 PersistentVolume 对象的访问权限：
 
 <!--
-- users (cluster operators) that need this access for their work, and who you trust,
-- the Kubernetes control plane components which creates PersistentVolumes based on PersistentVolumeClaims
+- Users (cluster operators) that need this access for their work, and who you trust,
+- The Kubernetes control plane components which creates PersistentVolumes based on PersistentVolumeClaims
   that are configured for automatic provisioning.
   This is usually setup by the Kubernetes provider or by the operator when installing a CSI driver.
 -->

content/ko/docs/reference/command-line-tools-reference/feature-gates.md renamed to content/ko/docs/reference/command-line-tools-reference/feature-gates/index.md

@@ -219,11 +219,11 @@ Kubernetes 配置可以用 YAML 或 JSON 定义。可以使用的文件扩展名
 
 <!--
 ```bash
-kubectl apply -f ./my-manifest.yaml            # create resource(s)
-kubectl apply -f ./my1.yaml -f ./my2.yaml      # create from multiple files
-kubectl apply -f ./dir                         # create resource(s) in all manifest files in dir
-kubectl apply -f https://git.io/vPieo          # create resource(s) from url
-kubectl create deployment nginx --image=nginx  # start a single instance of nginx
+kubectl apply -f ./my-manifest.yaml                 # create resource(s)
+kubectl apply -f ./my1.yaml -f ./my2.yaml           # create from multiple files
+kubectl apply -f ./dir                              # create resource(s) in all manifest files in dir
+kubectl apply -f https://example.com/manifest.yaml  # create resource(s) from url (Note: this is an example domain and does not contain a valid manifest)
+kubectl create deployment nginx --image=nginx       # start a single instance of nginx
 
 # create a Job which prints "Hello World"
 kubectl create job hello --image=busybox:1.28 -- echo "Hello World"
@@ -274,11 +274,11 @@ EOF
 ```
 -->
 ```bash
-kubectl apply -f ./my-manifest.yaml           # 创建资源
-kubectl apply -f ./my1.yaml -f ./my2.yaml     # 使用多个文件创建
-kubectl apply -f ./dir                        # 基于目录下的所有清单文件创建资源
-kubectl apply -f https://git.io/vPieo         # 从 URL 中创建资源
-kubectl create deployment nginx --image=nginx # 启动单实例 nginx
+kubectl apply -f ./my-manifest.yaml                  # 创建资源
+kubectl apply -f ./my1.yaml -f ./my2.yaml            # 使用多个文件创建
+kubectl apply -f ./dir                               # 基于目录下的所有清单文件创建资源
+kubectl apply -f https://example.com/manifest.yaml   # 从 URL 中创建资源（注意：这是一个示例域名，不包含有效的清单）
+kubectl create deployment nginx --image=nginx        # 启动单实例 nginx
 
 # 创建一个打印 “Hello World” 的 Job
 kubectl create job hello --image=busybox:1.28 -- echo "Hello World"