From cf8ddb9aed69574d5801ff1583affa3a46fe09cb Mon Sep 17 00:00:00 2001
From: howieyuen <haoyuan@mail.ustc.edu.cn>
Date: Fri, 31 Dec 2021 16:42:43 +0800
Subject: [PATCH] [zh]translate
 content/zh/docs/tutorials/security/cluster-level-pss.md

---
 .../tutorials/security/cluster-level-pss.md   | 444 ++++++++++++++++++
 1 file changed, 444 insertions(+)
 create mode 100644 content/zh/docs/tutorials/security/cluster-level-pss.md

diff --git a/content/zh/docs/tutorials/security/cluster-level-pss.md b/content/zh/docs/tutorials/security/cluster-level-pss.md
new file mode 100644
index 0000000000..0b4721c43b
--- /dev/null
+++ b/content/zh/docs/tutorials/security/cluster-level-pss.md
@@ -0,0 +1,444 @@
+---
+title: 在集群级别应用 Pod 安全标准
+content_type: tutorial
+weight: 10
+---
+<!-- 
+title: Apply Pod Security Standards at the Cluster Level
+content_type: tutorial
+weight: 10
+-->
+
+{{% alert title="Note" %}}
+<!-- This tutorial applies only for new clusters. -->
+本教程仅适用于新集群。
+{{% /alert %}}
+
+<!-- 
+Pod Security admission (PSA) is enabled by default in v1.23 and later, as it has
+[graduated to beta](/blog/2021/12/09/pod-security-admission-beta/).
+Pod Security
+is an admission controller that carries out checks against the Kubernetes
+[Pod Security Standards](docs/concepts/security/pod-security-standards/) when new pods are
+created. This tutorial shows you how to enforce the `baseline` Pod Security
+Standard at the cluster level which applies a standard configuration
+to all namespaces in a cluster.
+
+To apply Pod Security Standards to specific namespaces, refer to [Apply Pod Security Standards at the namespace level](/docs/tutorials/security/ns-level-pss).
+-->
+Pod 安全准入（PSA）在 v1.23 及更高版本默认启用，
+因为它[升级到测试版（beta）](/blog/2021/12/09/pod-security-admission-beta/)。
+Pod 安全准入是在创建 Pod 时应用
+[Pod 安全标准](/zh/docs/concepts/security/pod-security-standards/)的准入控制器。
+本教程将向你展示如何在集群级别实施 `baseline` Pod 安全标准，
+该标准将标准配置应用于集群中的所有名称空间。
+
+要将 Pod 安全标准应用于特定名字空间，
+请参阅[在名字空间级别应用 Pod 安全标准](/zh/docs/tutorials/security/ns-level-pss)。
+
+## {{% heading "prerequisites" %}}
+<!-- 
+Install the following on your workstation:
+
+- [KinD](https://kind.sigs.k8s.io/docs/user/quick-start/#installation)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
+-->
+在你的工作站中安装以下内容：
+
+- [KinD](https://kind.sigs.k8s.io/docs/user/quick-start/#installation)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
+
+<!--
+## Choose the right Pod Security Standard to apply
+
+[Pod Security Admission](/docs/concepts/security/pod-security-admission/)
+lets you apply built-in [Pod Security Standards](/docs/concepts/security/pod-security-standards/)
+with the following modes: `enforce`, `audit`, and `warn`.
+
+To gather information that helps you to choose the Pod Security Standards
+that are most appropriate for your configuration, do the following: 
+-->
+## 正确选择要应用的 Pod 安全标准  {#choose-the-right-pod-security-standard-to-apply}
+
+[Pod 安全准入](/zh/docs/concepts/security/pod-security-admission/)
+允许你使用以下模式应用内置的
+[Pod 安全标准](/zh/docs/concepts/security/pod-security-standards/):
+`enforce`、`audit` 和 `warn`。
+
+要收集信息以便选择最适合你的配置的 Pod 安全标准，请执行以下操作：
+
+<!-- 
+1. Create a cluster with no Pod Security Standards applied:
+ -->
+1. 创建一个没有应用 Pod 安全标准的集群：
+
+   ```shell
+   kind create cluster --name psa-wo-cluster-pss --image kindest/node:v1.23.0
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+   ```
+   Creating cluster "psa-wo-cluster-pss" ...
+   ✓ Ensuring node image (kindest/node:v1.23.0) 🖼
+   ✓ Preparing nodes 📦  
+   ✓ Writing configuration 📜
+   ✓ Starting control-plane 🕹️
+   ✓ Installing CNI 🔌
+   ✓ Installing StorageClass 💾
+   Set kubectl context to "kind-psa-wo-cluster-pss"
+   You can now use your cluster with:
+   
+   kubectl cluster-info --context kind-psa-wo-cluster-pss
+   
+   Thanks for using kind! 😊
+   
+   ```
+
+<!-- 
+1. Set the kubectl context to the new cluster:
+-->
+2. 将 kubectl 上下文设置为新集群：
+
+   ```shell
+   kubectl cluster-info --context kind-psa-wo-cluster-pss
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+
+   ```
+   Kubernetes control plane is running at https://127.0.0.1:61350 
+   CoreDNS is running at https://127.0.0.1:61350/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
+   
+   To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
+   ```
+
+<!-- 
+1. Get a list of namespaces in the cluster:
+-->
+3. 获取集群中的名字空间列表：
+
+   ```shell
+   kubectl get ns
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+   ```      
+   NAME                 STATUS   AGE
+   default              Active   9m30s
+   kube-node-lease      Active   9m32s
+   kube-public          Active   9m32s
+   kube-system          Active   9m32s
+   local-path-storage   Active   9m26s
+   ```
+
+<!-- 
+1. Use `--dry-run=server` to understand what happens when different Pod Security Standards
+   are applied:
+ -->
+4. 使用 `--dry-run=server` 来了解应用不同的 Pod 安全标准时会发生什么：
+
+   1. Privileged
+      ```shell
+      kubectl label --dry-run=server --overwrite ns --all \                    
+      pod-security.kubernetes.io/enforce=privileged
+      ```
+      <!-- The output is similar to this: -->
+      输出类似于：
+       ```      
+       namespace/default labeled
+       namespace/kube-node-lease labeled
+       namespace/kube-public labeled
+       namespace/kube-system labeled
+       namespace/local-path-storage labeled
+       ```
+   2. Baseline
+      ```shell    
+      kubectl label --dry-run=server --overwrite ns --all \
+      pod-security.kubernetes.io/enforce=baseline
+      ```
+      <!-- The output is similar to this: -->
+      输出类似于：
+      ```   
+      namespace/default labeled
+      namespace/kube-node-lease labeled
+      namespace/kube-public labeled
+      Warning: existing pods in namespace "kube-system" violate the new PodSecurity enforce level "baseline:latest"
+      Warning: etcd-psa-wo-cluster-pss-control-plane (and 3 other pods): host namespaces, hostPath volumes
+      Warning: kindnet-vzj42: non-default capabilities, host namespaces, hostPath volumes
+      Warning: kube-proxy-m6hwf: host namespaces, hostPath volumes, privileged
+      namespace/kube-system labeled
+      namespace/local-path-storage labeled
+      ```   
+
+   3. Restricted
+      ```shell
+      kubectl label --dry-run=server --overwrite ns --all \
+      pod-security.kubernetes.io/enforce=restricted
+      ```
+      <!-- The output is similar to this: -->
+      输出类似于：
+      ```   
+      namespace/default labeled
+      namespace/kube-node-lease labeled
+      namespace/kube-public labeled
+      Warning: existing pods in namespace "kube-system" violate the new PodSecurity enforce level "restricted:latest"
+      Warning: coredns-7bb9c7b568-hsptc (and 1 other pod): unrestricted capabilities, runAsNonRoot != true, seccompProfile
+      Warning: etcd-psa-wo-cluster-pss-control-plane (and 3 other pods): host namespaces, hostPath volumes, allowPrivilegeEscalation != false, unrestricted capabilities, restricted volume types, runAsNonRoot != true
+      Warning: kindnet-vzj42: non-default capabilities, host namespaces, hostPath volumes, allowPrivilegeEscalation != false, unrestricted capabilities, restricted volume types, runAsNonRoot != true, seccompProfile
+      Warning: kube-proxy-m6hwf: host namespaces, hostPath volumes, privileged, allowPrivilegeEscalation != false, unrestricted capabilities, restricted volume types, runAsNonRoot != true, seccompProfile
+      namespace/kube-system labeled
+      Warning: existing pods in namespace "local-path-storage" violate the new PodSecurity enforce level "restricted:latest"
+      Warning: local-path-provisioner-d6d9f7ffc-lw9lh: allowPrivilegeEscalation != false, unrestricted capabilities, runAsNonRoot != true, seccompProfile
+      namespace/local-path-storage labeled
+      ```
+
+<!-- 
+From the previous output, you'll notice that applying the `privileged` Pod Security Standard shows no warnings
+for any namespaces. However, `baseline` and `restricted` standards both have
+warnings, specifically in the `kube-system` namespace.
+-->
+从前面的输出中，你会注意到应用 `privileged` Pod 安全标准不会显示任何名字空间的警告。
+然而，`baseline` 和 `restricted` 标准都有警告，特别是在 `kube-system` 名字空间中。
+
+<!-- 
+## Set modes, versions and standards
+
+In this section, you apply the following Pod Security Standards to the `latest` version:
+
+* `baseline` standard in `enforce` mode.
+* `restricted` standard in `warn` and `audit` mode.
+-->
+## 设置模式、版本和标准  {#set-modes-versions-and-standards}
+
+在本节中，你将以下 Pod 安全标准应用于最新（`latest`）版本：
+
+* 在 `enforce` 模式下的 `baseline` 标准。
+* `warn` 和 `audit` 模式下的 `restricted` 标准。
+
+<!-- 
+The `baseline` Pod Security Standard provides a convenient
+middle ground that allows keeping the exemption list short and prevents known
+privilege escalations.
+
+Additionally, to prevent pods from failing in `kube-system`, you'll exempt the namespace
+from having Pod Security Standards applied.
+
+When you implement Pod Security Admission in your own environment, consider the
+following:
+-->
+`baseline` Pod 安全标准提供了一个方便的中间立场，能够保持豁免列表简短并防止已知的特权升级。
+
+此外，为了防止 `kube-system` 中的 Pod 失败，你将免除该名字空间应用 Pod 安全标准。
+
+在你自己的环境中实施 Pod 安全准入时，请考虑以下事项：
+
+<!-- 
+1. Based on the risk posture applied to a cluster, a stricter Pod Security
+   Standard like `restricted` might be a better choice.
+1. Exempting the `kube-system` namespace allows pods to run as
+   `privileged` in this namespace. For real world use, the Kubernetes project
+   strongly recommends that you apply strict RBAC
+   policies that limit access to `kube-system`, following the principle of least
+   privilege.
+   To implement the preceding standards, do the following:
+1. Create a configuration file that can be consumed by the Pod Security
+   Admission Controller to implement these Pod Security Standards:
+-->
+1. 根据应用于集群的风险状况，更严格的 Pod 安全标准（如 `restricted`）可能是更好的选择。
+2. 对 `kube-system` 名字空间进行赦免会允许 Pod 在其中以 `privileged` 模式运行。
+   对于实际使用，Kubernetes 项目强烈建议你应用严格的 RBAC 策略来限制对 `kube-system` 的访问，
+   遵循最小特权原则。
+3. 创建一个配置文件，Pod 安全准入控制器可以使用该文件来实现这些 Pod 安全标准：
+
+   ```
+   mkdir -p /tmp/pss
+   cat <<EOF > /tmp/pss/cluster-level-pss.yaml 
+   apiVersion: apiserver.config.k8s.io/v1
+   kind: AdmissionConfiguration
+   plugins:
+   - name: PodSecurity
+     configuration:
+       apiVersion: pod-security.admission.config.k8s.io/v1beta1
+       kind: PodSecurityConfiguration
+       defaults:
+         enforce: "baseline"
+         enforce-version: "latest"
+         audit: "restricted"
+         audit-version: "latest"
+         warn: "restricted"
+         warn-version: "latest"
+       exemptions:
+         usernames: []
+         runtimeClasses: []
+         namespaces: [kube-system]
+   EOF
+   ```
+
+<!-- 
+1. Configure the API server to consume this file during cluster creation:
+-->
+4. 在创建集群时配置 API 服务器使用此文件：
+
+   ```
+   cat <<EOF > /tmp/pss/cluster-config.yaml 
+   kind: Cluster
+   apiVersion: kind.x-k8s.io/v1alpha4
+   nodes:
+   - role: control-plane
+     kubeadmConfigPatches:
+     - |
+       kind: ClusterConfiguration
+       apiServer:
+           extraArgs:
+             admission-control-config-file: /etc/config/cluster-level-pss.yaml
+           extraVolumes:
+             - name: accf
+               hostPath: /etc/config
+               mountPath: /etc/config
+               readOnly: false
+               pathType: "DirectoryOrCreate"
+     extraMounts:
+     - hostPath: /tmp/pss
+       containerPath: /etc/config
+       # optional: if set, the mount is read-only.
+       # default false
+       readOnly: false
+       # optional: if set, the mount needs SELinux relabeling.
+       # default false
+       selinuxRelabel: false
+       # optional: set propagation mode (None, HostToContainer or Bidirectional)
+       # see https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
+       # default None
+       propagation: None
+   EOF
+   ```
+
+   {{<note>}}
+   <!-- 
+   If you use Docker Desktop with KinD on macOS, you can
+   add `/tmp` as a Shared Directory under the menu item
+   **Preferences > Resources > File Sharing**.
+   -->
+   如果你在 macOS 上使用 Docker Desktop 和 KinD，
+   你可以在菜单项 **Preferences > Resources > File Sharing**
+   下添加 `/tmp` 作为共享目录。
+   {{</note>}}
+
+<!-- 
+1. Create a cluster that uses Pod Security Admission to apply
+   these Pod Security Standards:
+-->
+5. 创建一个使用 Pod 安全准入的集群来应用这些 Pod 安全标准：
+
+   ```shell
+   kind create cluster --name psa-with-cluster-pss --image kindest/node:v1.23.0 --config /tmp/pss/cluster-config.yaml
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+   ```
+   Creating cluster "psa-with-cluster-pss" ...
+    ✓ Ensuring node image (kindest/node:v1.23.0) 🖼 
+    ✓ Preparing nodes 📦  
+    ✓ Writing configuration 📜 
+    ✓ Starting control-plane 🕹️ 
+    ✓ Installing CNI 🔌 
+    ✓ Installing StorageClass 💾 
+   Set kubectl context to "kind-psa-with-cluster-pss"
+   You can now use your cluster with:
+   
+   kubectl cluster-info --context kind-psa-with-cluster-pss
+   
+   Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂
+   ```
+
+<!-- 
+1. Point kubectl to the cluster
+-->
+6. 将 kubectl 指向集群
+
+   ```shell
+   kubectl cluster-info --context kind-psa-with-cluster-pss
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+   ```
+   Kubernetes control plane is running at https://127.0.0.1:63855
+   CoreDNS is running at https://127.0.0.1:63855/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
+ 
+   To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
+   ```
+
+<!-- 
+1. Create the following Pod specification for a minimal configuration in the default namespace:
+-->
+7. 创建以下 Pod 规约作为在 default 名字空间中的一个最小配置：
+
+   ```
+   cat <<EOF > /tmp/pss/nginx-pod.yaml
+   apiVersion: v1
+   kind: Pod
+   metadata:
+     name: nginx
+   spec:
+     containers:
+       - image: nginx
+         name: nginx
+         ports:
+           - containerPort: 80
+   EOF
+   ```
+
+<!-- 
+1. Create the Pod in the cluster:
+-->
+8. 在集群中创建 Pod：
+
+   ```shell
+   kubectl apply -f /tmp/pss/nginx-pod.yaml
+   ```
+   <!-- The output is similar to this: -->
+   输出类似于：
+   ```
+   Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "nginx" must set securityContext allowPrivilegeEscalation=false), unrestricted capabilities (container "nginx" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "nginx" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "nginx" must set securityContext seccompProfile.type to "RuntimeDefault" or "Localhost")
+   pod/nginx created
+   ```
+
+<!-- 
+## Clean up
+
+Run `kind delete cluster -name psa-with-cluster-pss` and
+`kind delete cluster -name psa-wo-cluster-pss` to delete the clusters you
+created.
+-->
+## 清理  {#clean-up}
+
+运行 `kind delete cluster -name psa-with-cluster-pss` 和
+`kind delete cluster -name psa-wo-cluster-pss` 来删除你创建的集群。
+
+## {{% heading "whatsnext" %}}
+
+<!-- 
+- Run a
+  [shell script](/examples/security/kind-with-cluster-level-baseline-pod-security.sh)
+  to perform all the preceding steps at once:
+  1. Create a Pod Security Standards based cluster level Configuration
+  2. Create a file to let API server consumes this configuration
+  3. Create a cluster that creates an API server with this configuration
+  4. Set kubectl context to this new cluster
+  5. Create a minimal pod yaml file
+  6. Apply this file to create a Pod in the new cluster
+- [Pod Security Admission](/docs/concepts/security/pod-security-admission/)
+- [Pod Security Standards](/docs/concepts/security/pod-security-standards/)
+- [Apply Pod Security Standards at the namespace level](/docs/tutorials/security/ns-level-pss/)
+-->
+- 运行一个 [shell 脚本](/zh/examples/security/kind-with-cluster-level-baseline-pod-security.sh)
+  一次执行前面的所有步骤：
+  1. 创建一个基于 Pod 安全标准的集群级别配置
+  2. 创建一个文件让 API 服务器消费这个配置
+  3. 创建一个集群，用这个配置创建一个 API 服务器
+  4. 设置 kubectl 上下文为这个新集群
+  5. 创建一个最小的 Pod yaml 文件
+  6. 应用这个文件，在新集群中创建一个 Pod
+- [Pod 安全准入](/zh/docs/concepts/security/pod-security-admission/)
+- [Pod 安全标准](/zh/docs/concepts/security/pod-security-standards/)
+- [在名字空间级别应用 Pod 安全标准](/zh/docs/tutorials/security/ns-level-pss/)
\ No newline at end of file