Merge pull request #46341 from windsonsea/glossyh

[zh] Sync 4 files in reference/glossary

Author: k8s-ci-robot

content/zh-cn/docs/reference/glossary/cri-o.md

@@ -22,6 +22,7 @@ aka:
 tags:
 - tool
 -->
+
 <!-- 
 A tool that lets you use OCI container runtimes with Kubernetes CRI.
 -->
@@ -38,13 +39,13 @@ runtimes that are compatible with the Open Container Initiative (OCI)
 CRI-O 是 {{< glossary_tooltip text="CRI" term_id="cri" >}} 的一种实现，
 使得你可以使用与开放容器倡议（Open Container Initiative；OCI）
 [运行时规范](https://www.github.com/opencontainers/runtime-spec)
-兼容的{{< glossary_tooltip text="容器" term_id="container" >}}。
+兼容的{{< glossary_tooltip text="容器" term_id="container" >}}运行时。
 
 <!-- 
 Deploying CRI-O allows Kubernetes to use any OCI-compliant runtime as the container
 runtime for running {{< glossary_tooltip text="Pods" term_id="pod" >}}, and to fetch
 OCI container images from remote registries.
 -->
-部署 CRI-O 允许 Kubernetes 使用任何符合 OCI 要求的运行时作为容器运行时
-去运行 {{< glossary_tooltip text="Pod" term_id="pod" >}}，
+部署 CRI-O 允许 Kubernetes 使用任何符合 OCI 要求的运行时作为容器运行时去运行
+{{< glossary_tooltip text="Pod" term_id="pod" >}}，
 并从远程容器仓库获取 OCI 容器镜像。

content/zh-cn/docs/reference/glossary/index.md

@@ -2,6 +2,7 @@
 title: 词汇表
 layout: glossary
 noedit: true
+body_class: glossary
 default_active_tag: fundamental
 weight: 5
 card:
@@ -16,6 +17,7 @@ approvers:
 title: Glossary
 layout: glossary
 noedit: true
+body_class: glossary
 default_active_tag: fundamental
 weight: 5
 card:

content/zh-cn/docs/reference/glossary/priority-class.md

@@ -0,0 +1,42 @@
+---
+title: PriorityClass
+id: priority-class
+date: 2024-03-19
+full_link: /zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass
+short_description: >
+  从类别名称到 Pod 本身调度优先级的映射。
+aka:
+tags:
+- core-object
+---
+<!--
+title: PriorityClass
+id: priority-class
+date: 2024-03-19
+full_link: /docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass
+short_description: >
+  A mapping from a class name to the scheduling priority that a Pod should have.
+aka:
+tags:
+- core-object
+-->
+
+<!--
+A PriorityClass is a named class for the scheduling priority that should be assigned to a Pod
+in that class.
+-->
+PriorityClass 是针对应分配给此类别 Pod 的调度优先级而命名的一种类别。
+
+<!--more-->
+
+<!--
+A [PriorityClass](/docs/concepts/scheduling-eviction/pod-priority-preemption/#how-to-use-priority-and-preemption)
+is a non-namespaced object mapping a name to an integer priority, used for a Pod. The name is
+specified in the `metadata.name` field, and the priority value in the `value` field. Priorities range from
+-2147483648 to 1000000000 inclusive. Higher values indicate higher priority.
+-->
+[PriorityClass](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#how-to-use-priority-and-preemption)
+是用于 Pod 的一个非命名空间对象，负责将某个名称映射到一个整数优先级。
+此名称在 `metadata.name` 字段中指定，优先级值在 `value` 字段中指定。
+优先级范围从 -2147483648 到 1000000000（包含边界值）。
+值越大，优先级越高。

content/zh-cn/docs/reference/glossary/spec.md

@@ -0,0 +1,49 @@
+---
+title: Spec
+id: spec
+date: 2023-12-17
+full_link: /zh-cn/docs/concepts/overview/working-with-objects/#object-spec-and-status
+short_description: >
+  在 Kubernetes 清单中的此字段用来定义特定 Kubernetes 对象的预期状态或预期配置。
+
+aka:
+tags:
+- fundamental
+- architecture
+---
+<!--
+title: Spec
+id: spec
+date: 2023-12-17
+full_link: /docs/concepts/overview/working-with-objects/#object-spec-and-status
+short_description: >
+  This field in Kubernetes manifests defines the desired state or configuration for specific Kubernetes objects.
+
+aka:
+tags:
+- fundamental
+- architecture
+-->
+
+<!--
+Defines how each object, like Pods or Services, should be configured and its desired state.
+-->
+定义 Pod 或 Service 这类每种对象应被如何配置及其预期状态。
+
+<!--more-->
+
+<!--
+Almost every Kubernetes object includes two nested object fields that govern the object's configuration: the object spec and the object status. For objects that have a spec, you have to set this when you create the object, providing a description of the characteristics you want the resource to have: its desired state.
+-->
+几乎每个 Kubernetes 对象都包含两个嵌套的对象字段，用于治理对象本身的配置：
+对象规约（spec）和对象状态（status）。
+对于具有规约的对象，你必须在创建对象时设置规约，并提供资源所需特征的描述：即其预期状态。
+
+<!--
+It varies for different objects like Pods, StatefulSets, and Services, detailing settings such as containers, volumes, replicas, ports,   
+and other specifications unique to each object type. This field encapsulates what state Kubernetes should maintain for the defined   
+object.
+-->
+此字段对于 Pod、StatefulSet 和 Service 等不同对象会有所差异，
+字段详细说明如容器、卷、副本、端口等设置以及每种对象特有的其他规约。
+此字段封装了 Kubernetes 针对所定义的对象应保持何种状态。