[zh-cn] sync volume-attributes-classes.md install-kubectl-linux.md

Signed-off-by: xin.li <[email protected]>

Author: my-git9

content/zh-cn/docs/concepts/storage/volume-attributes-classes.md

@@ -14,7 +14,7 @@ weight: 40
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
+{{< feature-state feature_gate_name="VolumeAttributesClass" >}}
 
 <!--
 This page assumes that you are familiar with [StorageClasses](/docs/concepts/storage/storage-classes/),
@@ -30,26 +30,40 @@ in Kubernetes.
 <!--
 A VolumeAttributesClass provides a way for administrators to describe the mutable
 "classes" of storage they offer. Different classes might map to different quality-of-service levels.
-Kubernetes itself is unopinionated about what these classes represent.
+Kubernetes itself is un-opinionated about what these classes represent.
 
-This is an alpha feature and disabled by default.
+This is a beta feature and disabled by default.
 
-If you want to test the feature whilst it's alpha, you need to enable the `VolumeAttributesClass`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kube-controller-manager and the kube-apiserver. You use the `--feature-gates` command line argument:
+If you want to test the feature whilst it's beta, you need to enable the `VolumeAttributesClass`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kube-controller-manager
+and the kube-apiserver. You use the `--feature-gates` command line argument:
 -->
 卷属性类（VolumeAttributesClass）为管理员提供了一种描述可变更的存储“类”的方法。
 不同的类可以映射到不同的服务质量级别。Kubernetes 本身不关注这些类代表什么。
 
-这是一个 Alpha 特性，默认被禁用。
+这是一个 Beta 特性，默认被禁用。
 
-如果你想测试这一处于 Alpha 阶段的特性，你需要为 kube-controller-manager 和 kube-apiserver 启用
+如果你想测试这一处于 Beta 阶段的特性，你需要为 kube-controller-manager 和 kube-apiserver 启用
 `VolumeAttributesClass` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
 你可以使用 `--feature-gates` 命令行参数：
 
-```
+```shell
 --feature-gates="...,VolumeAttributesClass=true"
 ```
 
+<!--
+You will also have to enable the `storage.k8s.io/v1beta1` API group through the
+`kube-apiserver` [runtime-config](https://kubernetes.io/docs/tasks/administer-cluster/enable-disable-api/).
+You use the following command line argument:
+-->
+你还必须通过 `kube-apiserver`
+[运行时配置](/zh-cn/docs/tasks/administer-cluster/enable-disable-api/)启用
+`storage.k8s.io/v1beta1` API 组：
+
+```shell
+--runtime-config=storage.k8s.io/v1beta1=true
+```
+
 <!--
 You can also only use VolumeAttributesClasses with storage backed by
 {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}}, and only where the
@@ -80,7 +94,7 @@ VolumeAttributesClass 对象的名称比较重要，用户用对象名称来请
 但现有类中的参数是不可变的。
 
 ```yaml
-apiVersion: storage.k8s.io/v1alpha1
+apiVersion: storage.k8s.io/v1beta1
 kind: VolumeAttributesClass
 metadata:
   name: silver
@@ -90,13 +104,14 @@ parameters:
   provisioned-throughput: "50" 
 ```
 
-
 <!--
 ### Provisioner
 
-Each VolumeAttributesClass has a provisioner that determines what volume plugin is used for provisioning PVs. The field `driverName` must be specified. 
+Each VolumeAttributesClass has a provisioner that determines what volume plugin is used for
+provisioning PVs. The field `driverName` must be specified. 
 
-The feature support for VolumeAttributesClass is implemented in [kubernetes-csi/external-provisioner](https://github.com/kubernetes-csi/external-provisioner).
+The feature support for VolumeAttributesClass is implemented in
+[kubernetes-csi/external-provisioner](https://github.com/kubernetes-csi/external-provisioner).
 -->
 ### 存储制备器   {#provisioner}
 
@@ -107,7 +122,8 @@ The feature support for VolumeAttributesClass is implemented in [kubernetes-csi/
 [kubernetes-csi/external-provisioner](https://github.com/kubernetes-csi/external-provisioner) 中实现。
 
 <!--
-You are not restricted to specifying the [kubernetes-csi/external-provisioner](https://github.com/kubernetes-csi/external-provisioner). You can also run and specify external provisioners,
+You are not restricted to specifying the [kubernetes-csi/external-provisioner](https://github.com/kubernetes-csi/external-provisioner).
+You can also run and specify external provisioners,
 which are independent programs that follow a specification defined by Kubernetes.
 Authors of external provisioners have full discretion over where their code lives, how
 the provisioner is shipped, how it needs to be run, what volume plugin it uses, etc.
@@ -119,11 +135,13 @@ the provisioner is shipped, how it needs to be run, what volume plugin it uses,
 <!--
 ### Resizer
 
-Each VolumeAttributesClass has a resizer that determines what volume plugin is used for modifying PVs. The field `driverName` must be specified. 
+Each VolumeAttributesClass has a resizer that determines what volume plugin is used
+for modifying PVs. The field `driverName` must be specified. 
 
-The modifying volume feature support for VolumeAttributesClass is implemented in [kubernetes-csi/external-resizer](https://github.com/kubernetes-csi/external-resizer).
+The modifying volume feature support for VolumeAttributesClass is implemented in
+[kubernetes-csi/external-resizer](https://github.com/kubernetes-csi/external-resizer).
 
-For example, a existing PersistentVolumeClaim is using a VolumeAttributesClass named silver:
+For example, an existing PersistentVolumeClaim is using a VolumeAttributesClass named silver:
 -->
 ### 调整器   {#resizer}
 
@@ -152,7 +170,7 @@ A new VolumeAttributesClass gold is available in the cluster:
 集群中有一个新的名为 gold 的 VolumeAttributesClass：
 
 ```yaml
-apiVersion: storage.k8s.io/v1alpha1
+apiVersion: storage.k8s.io/v1beta1
 kind: VolumeAttributesClass
 metadata:
   name: gold
@@ -183,10 +201,10 @@ spec:
 
 VolumeAttributeClasses have parameters that describe volumes belonging to them. Different parameters may be accepted
 depending on the provisioner or the resizer. For example, the value `4000`, for the parameter `iops`,
-and the parameter `throughput` are specific to GCE PD. 
+and the parameter `throughput` are specific to GCE PD.
 When a parameter is omitted, the default is used at volume provisioning.
-If a user apply the PVC with a different VolumeAttributesClass with omitted parameters, the default value of
-the parameters may be used depends on the CSI driver implementation.
+If a user applies the PVC with a different VolumeAttributesClass with omitted parameters, the default value of
+the parameters may be used depending on the CSI driver implementation.
 Please refer to the related CSI driver documentation for more details.
 -->
 ## 参数   {#parameters}

content/zh-cn/docs/tasks/tools/install-kubectl-linux.md

@@ -47,7 +47,7 @@ The following methods exist for installing kubectl on Linux:
 <!--
 ### Install kubectl binary with curl on Linux
 -->
-### 用 curl 在 Linux 系统中安装 kubectl {#install-kubectl-binary-with-curl-on-linux}
+### 用 curl 在 Linux 系统中安装 kubectl  {#install-kubectl-binary-with-curl-on-linux}
 
 <!--
 1. Download the latest release with the command:
@@ -145,7 +145,7 @@ The following methods exist for installing kubectl on Linux:
 <!--
 1. Install kubectl
 -->
-3. 安装 kubectl
+3. 安装 kubectl：
 
    ```bash
    sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
@@ -380,9 +380,46 @@ To upgrade kubectl to another minor release, you'll need to bump the version in
 {{< /note >}}
 
 <!--
-2. Install kubectl using `zypper`:
+2. Update `zypper` and confirm the new repo addition:
 -->
-2. 使用 `zypper` 安装 kubectl：
+2. 更新 zypper 并确认新的仓库已添加：
+
+   ```bash
+   sudo zypper update
+   ```
+
+   <!--
+   When this message appears, press 't' or 'a':
+   -->
+   出现此信息时，按 't' 或 'a''：
+
+   ```
+   New repository or package signing key received:
+
+   Repository:       Kubernetes
+   Key Fingerprint:  1111 2222 3333 4444 5555 6666 7777 8888 9999 AAAA
+   Key Name:         isv:kubernetes OBS Project <isv:[email protected]>
+   Key Algorithm:    RSA 2048
+   Key Created:      Thu 25 Aug 2022 01:21:11 PM -03
+   Key Expires:      Sat 02 Nov 2024 01:21:11 PM -03 (expires in 85 days)
+   Rpm Name:         gpg-pubkey-9a296436-6307a177
+
+   Note: Signing data enables the recipient to verify that no modifications occurred after the data
+   were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
+   and in extreme cases even to a system compromise.
+
+   Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
+   you are not sure whether the presented key is authentic, ask the repository provider or check
+   their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
+   are using.
+
+   Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
+   ```
+
+<!--
+3. Install kubectl using `zypper`:
+-->
+3. 使用 `zypper` 安装 kubectl：
 
    ```bash
    sudo zypper install -y kubectl