[zh-cn] sync windows/_index.md dual-stack.md

my-git9 · my-git9 · commit 219fc9a89cf4 · 2023-05-11T22:48:20.000+08:00
field-selectors.md finalizers.md names.md

Signed-off-by: xin.li &lt;xin.li@daocloud.io&gt;
diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/field-selectors.md b/content/zh-cn/docs/concepts/overview/working-with-objects/field-selectors.md
@@ -11,9 +11,12 @@ weight: 70
 
 <!--
 _Field selectors_ let you [select Kubernetes resources](/docs/concepts/overview/working-with-objects/kubernetes-objects) based on the value of one or more resource fields. Here are some examples of field selector queries:
+
+_Field selectors_ let you select Kubernetes {{< glossary_tooltip text="objects" term_id="object" >}} based on the
+value of one or more resource fields. Here are some examples of field selector queries:
 -->
-“字段选择器（Field selectors）”允许你根据一个或多个资源字段的值
-[筛选 Kubernetes 资源](/zh-cn/docs/concepts/overview/working-with-objects/kubernetes-objects)。
+“字段选择器（Field selectors）”允许你根据一个或多个资源字段的值筛选
+Kubernetes {{< glossary_tooltip text="对象" term_id="object" >}}。
 下面是一些使用字段选择器查询的例子：
 
 * `metadata.name=my-service`
@@ -23,7 +26,8 @@ _Field selectors_ let you [select Kubernetes resources](/docs/concepts/overview/
 <!--
 This `kubectl` command selects all Pods for which the value of the [`status.phase`](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase) field is `Running`:
 -->
-下面这个 `kubectl` 命令将筛选出 [`status.phase`](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)
+下面这个 `kubectl` 命令将筛选出
+[`status.phase`](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)
 字段值为 `Running` 的所有 Pod：
 
 ```shell
@@ -36,7 +40,8 @@ Field selectors are essentially resource *filters*. By default, no selectors/fil
 -->
 字段选择器本质上是资源“过滤器（Filters）”。默认情况下，字段选择器/过滤器是未被应用的，
 这意味着指定类型的所有资源都会被筛选出来。
-这使得 `kubectl get pods` 和 `kubectl get pods --field-selector ""` 这两个 `kubectl` 查询是等价的。
+这使得 `kubectl get pods` 和 `kubectl get pods --field-selector ""`
+这两个 `kubectl` 查询是等价的。
 
 {{< /note >}}
 
diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/finalizers.md b/content/zh-cn/docs/concepts/overview/working-with-objects/finalizers.md
@@ -8,6 +8,14 @@ weight: 80
 
 {{<glossary_definition term_id="finalizer" length="long">}}
 
+<!--
+You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
+of {{< glossary_tooltip text="objects" term_id="object" >}} by alerting {{<glossary_tooltip text="controllers" term_id="controller">}}
+to perform specific cleanup tasks before deleting the target resource.
+-->
+你可以使用 Finalizers 来控制{{< glossary_tooltip text="对象" term_id="object" >}}的{{<glossary_tooltip text="垃圾回收" term_id="garbage-collection">}}，
+方法是在删除目标资源之前提醒{{<glossary_tooltip text="控制器" term_id="controller">}}执行特定的清理任务。
+
 <!--
 Finalizers don't usually specify the code to execute. Instead, they are
 typically lists of keys on a specific resource similar to annotations.
diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/names.md b/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
@@ -15,13 +15,13 @@ weight: 30
 <!-- overview -->
 
 <!--
-Each object in your cluster has a [_Name_](#names) that is unique for that type of resource.
+Each {{< glossary_tooltip text="object" term_id="object" >}} in your cluster has a [_Name_](#names) that is unique for that type of resource.
 Every Kubernetes object also has a [_UID_](#uids) that is unique across your whole cluster.
 
 For example, you can only have one Pod named `myapp-1234` within the same [namespace](/docs/concepts/overview/working-with-objects/namespaces/), but you can have one Pod and one Deployment that are each named `myapp-1234`.
 -->
 
-集群中的每一个对象都有一个[**名称**](#names)来标识在同类资源中的唯一性。
+集群中的每一个{{< glossary_tooltip text="对象" term_id="object" >}}都有一个[**名称**](#names)来标识在同类资源中的唯一性。
 
 每个 Kubernetes 对象也有一个 [**UID**](#uids) 来标识在整个集群中的唯一性。
 
diff --git a/content/zh-cn/docs/concepts/services-networking/dual-stack.md b/content/zh-cn/docs/concepts/services-networking/dual-stack.md
@@ -150,6 +150,18 @@ IPv6 CIDR 的一个例子：`fdXY:IJKL:MNOP:15::/64`
 （这里演示的是格式而非有效地址 - 请看 [RFC 4193](https://tools.ietf.org/html/rfc4193)）。
 {{< /note >}}
 
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+<!--
+When using an external cloud provider, you can pass a dual-stack `--node-ip` value to
+kubelet if you enable the `CloudDualStackNodeIPs` feature gate in both kubelet and the
+external cloud provider. This is only supported for cloud providers that support dual
+stack clusters.
+-->
+使用外部云驱动时，如果你在 kubelet 和外部云提供商中都启用了
+`CloudDualStackNodeIPs` 特性门控，则可以将双栈 `--node-ip`
+值传递给 kubelet。此特性需要保证云提供商支持双栈集群。
+
 <!--
 ## Services
 -->
diff --git a/content/zh-cn/docs/concepts/windows/_index.md b/content/zh-cn/docs/concepts/windows/_index.md
@@ -1,8 +1,71 @@
 ---
 title: "Kubernetes 中的 Windows"
-weight: 50
+simple_list: true
+weight: 200
+description: >-
+  Kubernetes 支持运行 Microsoft Windows 节点。
 ---
+
 <!--
 title: "Windows in Kubernetes"
-weight: 50
+simple_list: true
+weight: 200 # late in list
+description: >-
+  Kubernetes supports nodes that run Microsoft Windows.
 -->
+
+<!--
+Kubernetes supports worker {{< glossary_tooltip text="nodes" term_id="node" >}}
+running either Linux or Microsoft Windows.
+-->
+Kubernetes 支持运行 Linux 或 Microsoft Windows
+的工作{{< glossary_tooltip text="节点" term_id="node" >}}。
+
+{{% thirdparty-content single="true" %}}
+
+<!--
+The CNCF and its parent the Linux Foundation take a vendor-neutral approach
+towards compatibility. It is possible to join your [Windows server](https://www.microsoft.com/en-us/windows-server)
+as a worker node to a Kubernetes cluster.
+-->
+CNCF 及其母公司 Linux 基金会采用供应商中立的方法来实现兼容性。可以将你的
+[Windows 服务器](https://www.microsoft.com/en-us/windows-server)作为工作节点加入
+Kubernetes 集群。
+
+<!--
+You can [install and set up kubectl on Windows](/docs/tasks/tools/install-kubectl-windows/)
+no matter what operating system you use within your cluster.
+
+If you are using Windows nodes, you can read:
+-->
+无论你的集群使用什么操作系统，
+都可以[在 Windows 上安装和设置 kubectl](/zh-cn/docs/tasks/tools/install-kubectl-windows/)。
+
+如果你使用的是 Windows 节点，你可以阅读：
+
+<!--
+* [Networking On Windows](/docs/concepts/services-networking/windows-networking/)
+* [Windows Storage In Kubernetes](/docs/concepts/storage/windows-storage/)
+* [Resource Management for Windows Nodes](/docs/concepts/configuration/windows-resource-management/)
+* [Configure RunAsUserName for Windows Pods and Containers](/docs/tasks/configure-pod-container/configure-runasusername/)
+* [Create A Windows HostProcess Pod](/docs/tasks/configure-pod-container/create-hostprocess-pod/)
+* [Configure Group Managed Service Accounts for Windows Pods and Containers](/docs/tasks/configure-pod-container/configure-gmsa/)
+* [Security For Windows Nodes](/docs/concepts/security/windows-security/)
+* [Windows Debugging Tips](/docs/tasks/debug/debug-cluster/windows/)
+* [Guide for Scheduling Windows Containers in Kubernetes](/docs/concepts/windows/user-guide)
+
+or, for an overview, read:
+-->
+* [Windows 上的网络](/zh-cn/docs/concepts/services-networking/windows-networking/)
+* [Kubernetes 中的 Windows 存储](/zh-cn/docs/concepts/storage/windows-storage/)
+* [Windows 节点的资源管理](/zh-cn/docs/concepts/configuration/windows-resource-management/)
+* [为 Windows Pod 和容器配置 RunAsUserName](/zh-cn/docs/tasks/configure-pod-container/configure-runasusername/)
+* [创建 Windows HostProcess Pod](/zh-cn/docs/tasks/configure-pod-container/create-hostprocess-pod/)
+* [为 Windows Pod 和容器配置组托管服务帐户](/zh-cn/docs/tasks/configure-pod-container/configure-gmsa/)
+* [Windows 节点的安全性](/zh-cn/docs/concepts/security/windows-security/)
+* [Windows 调试技巧](/zh-cn/docs/tasks/debug/debug-cluster/windows/)
+* [在 Kubernetes 中调度 Windows 容器指南](/zh-cn/docs/concepts/windows/user-guide)
+
+或者，要了解概览，请阅读：
+
+
