Merge pull request #34146 from LeeLin2602/main
[zh] improve translation for node componentspull/34184/head
commit
3649e83eca
|
@ -141,7 +141,7 @@ Node components run on every node, maintaining running pods and providing the Ku
|
|||
-->
|
||||
## Node 组件 {#node-components}
|
||||
|
||||
节点组件在每个节点上运行,维护运行的 Pod 并提供 Kubernetes 运行环境。
|
||||
节点组件会在每个节点上运行,负责维护运行的 Pod 并提供 Kubernetes 运行环境。
|
||||
|
||||
### kubelet
|
||||
|
||||
|
@ -203,11 +203,12 @@ Kubernetes 启动的容器自动将此 DNS 服务器包含在其 DNS 搜索列
|
|||
|
||||
[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications running in the cluster, as well as the cluster itself.
|
||||
-->
|
||||
### Web 界面(仪表盘)
|
||||
### Web 界面(仪表盘) {#web-ui-dashboard}
|
||||
|
||||
[Dashboard](/zh/docs/tasks/access-application-cluster/web-ui-dashboard/)
|
||||
是 Kubernetes 集群的通用的、基于 Web 的用户界面。
|
||||
它使用户可以管理集群中运行的应用程序以及集群本身并进行故障排除。
|
||||
它使用户可以管理集群中运行的应用程序以及集群本身,
|
||||
并进行故障排除。
|
||||
|
||||
<!--
|
||||
### Container Resource Monitoring
|
||||
|
@ -215,10 +216,11 @@ Kubernetes 启动的容器自动将此 DNS 服务器包含在其 DNS 搜索列
|
|||
[Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/) records generic time-series metrics
|
||||
about containers in a central database, and provides a UI for browsing that data.
|
||||
-->
|
||||
### 容器资源监控
|
||||
### 容器资源监控 {#container-resource-monitoring}
|
||||
|
||||
[容器资源监控](/zh/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
|
||||
将关于容器的一些常见的时间序列度量值保存到一个集中的数据库中,并提供用于浏览这些数据的界面。
|
||||
将关于容器的一些常见的时间序列度量值保存到一个集中的数据库中,
|
||||
并提供浏览这些数据的界面。
|
||||
|
||||
<!--
|
||||
### Cluster-level Logging
|
||||
|
@ -226,10 +228,11 @@ about containers in a central database, and provides a UI for browsing that data
|
|||
A [cluster-level logging](/docs/concepts/cluster-administration/logging/) mechanism is responsible for
|
||||
saving container logs to a central log store with search/browsing interface.
|
||||
-->
|
||||
### 集群层面日志
|
||||
### 集群层面日志 {#cluster-level-logging}
|
||||
|
||||
[集群层面日志](/zh/docs/concepts/cluster-administration/logging/) 机制负责将容器的日志数据
|
||||
保存到一个集中的日志存储中,该存储能够提供搜索和浏览接口。
|
||||
[集群层面日志](/zh/docs/concepts/cluster-administration/logging/)
|
||||
机制负责将容器的日志数据保存到一个集中的日志存储中,
|
||||
这种集中日志存储提供搜索和浏览接口。
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
|
|
|
@ -4,7 +4,7 @@ id: cluster
|
|||
date: 2019-06-15
|
||||
full_link:
|
||||
short_description: >
|
||||
集群由一组被称作节点的机器组成。这些节点上运行 Kubernetes 所管理的容器化应用。集群具有至少一个工作节点。
|
||||
集群由一组被称作节点的机器组成。这些节点上运行 Kubernetes 所管理的容器化应用。集群具有至少一个工作节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
@ -32,9 +32,9 @@ tags:
|
|||
A set of worker machines, called {{< glossary_tooltip text="nodes" term_id="node" >}},
|
||||
that run containerized applications. Every cluster has at least one worker node.
|
||||
-->
|
||||
集群是由一组被称作节点的机器组成,这些节点上会运行由 Kubernetes 所管理的容器化应用。
|
||||
集群是由一组被称作{{< glossary_tooltip text="节点(node)" term_id="node" >}}的机器组成,
|
||||
这些节点上会运行由 Kubernetes 所管理的容器化应用。
|
||||
且每个集群至少有一个工作节点。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
The worker node(s) host the {{< glossary_tooltip text="Pods" term_id="pod" >}} that are
|
||||
|
|
|
@ -41,8 +41,9 @@ Kubernetes supports container runtimes such sa
|
|||
and any other implementation of the [Kubernetes CRI (Container Runtime
|
||||
Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md).
|
||||
-->
|
||||
Kubernetes 支持容器运行时,例如
|
||||
Kubernetes 支持许多容器运行环境,例如
|
||||
{{< glossary_tooltip term_id="docker">}}、
|
||||
{{< glossary_tooltip term_id="containerd" >}}、{{< glossary_tooltip term_id="cri-o" >}}
|
||||
{{< glossary_tooltip term_id="containerd" >}}、
|
||||
{{< glossary_tooltip term_id="cri-o" >}}
|
||||
以及 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)
|
||||
的其他任何实现。
|
|
@ -29,15 +29,19 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
Control plane component that runs {{< glossary_tooltip text="controller" term_id="controller" >}} processes.
|
||||
Control plane component that runs
|
||||
{{< glossary_tooltip text="controller" term_id="controller" >}} processes.
|
||||
-->
|
||||
`kube-controller-manager` 是{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件,
|
||||
[kube-controller-manager](/zh/docs/reference/command-line-tools-reference/kube-controller-manager/) 是{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件,
|
||||
负责运行{{< glossary_tooltip text="控制器" term_id="controller" >}}进程。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.
|
||||
Logically, each {{< glossary_tooltip text="controller" term_id="controller" >}}
|
||||
is a separate process, but to reduce complexity,
|
||||
they are all compiled into a single binary and run in a single process.
|
||||
-->
|
||||
从逻辑上讲,每个{{< glossary_tooltip text="控制器" term_id="controller" >}}都是一个单独的进程,
|
||||
从逻辑上讲,
|
||||
每个{{< glossary_tooltip text="控制器" term_id="controller" >}}都是一个单独的进程,
|
||||
但是为了降低复杂性,它们都被编译到同一个可执行文件,并在同一个进程中运行。
|
||||
|
||||
|
|
|
@ -24,19 +24,30 @@ tags:
|
|||
- fundamental
|
||||
- networking
|
||||
--- -->
|
||||
<!-- [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) is a
|
||||
network proxy that runs on each node in your cluster, implementing part of
|
||||
the Kubernetes {{< glossary_tooltip term_id="service">}} concept. -->
|
||||
[kube-proxy](/zh/docs/reference/command-line-tools-reference/kube-proxy/) 是集群中每个节点上运行的网络代理,
|
||||
<!--
|
||||
kube-proxy is a network proxy that runs on each
|
||||
{{< glossary_tooltip text="node" term_id="node" >}} in your cluster,
|
||||
implementing part of the Kubernetes
|
||||
{{< glossary_tooltip term_id="service">}} concept.
|
||||
-->
|
||||
[kube-proxy](/zh/docs/reference/command-line-tools-reference/kube-proxy/)
|
||||
是集群中每个{{< glossary_tooltip text="节点(node)" term_id="node" >}}所上运行的网络代理,
|
||||
实现 Kubernetes {{< glossary_tooltip term_id="service">}} 概念的一部分。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- kube-proxy maintains network rules on nodes. These network rules allow
|
||||
network communication to your Pods from network sessions inside or outside
|
||||
of your cluster. -->
|
||||
kube-proxy 维护节点上的网络规则。这些网络规则允许从集群内部或外部的网络会话与 Pod 进行网络通信。
|
||||
<!--
|
||||
[kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/)
|
||||
maintains network rules on nodes. These network rules allow network
|
||||
communication to your Pods from network sessions inside or outside of
|
||||
your cluster.
|
||||
-->
|
||||
kube-proxy 维护节点上的一些网络规则,
|
||||
这些网络规则会允许从集群内部或外部的网络会话与 Pod 进行网络通信。
|
||||
|
||||
<!-- kube-proxy uses the operating system packet filtering layer if there is one
|
||||
and it's available. Otherwise, kube-proxy forwards the traffic itself. -->
|
||||
如果操作系统提供了数据包过滤层并可用的话,kube-proxy 会通过它来实现网络规则。否则, kube-proxy 仅转发流量本身。
|
||||
<!--
|
||||
kube-proxy uses the operating system packet filtering layer if there is one
|
||||
and it's available. Otherwise, kube-proxy forwards the traffic itself.
|
||||
-->
|
||||
如果操作系统提供了可用的数据包过滤层,则 kube-proxy 会通过它来实现网络规则。
|
||||
否则,kube-proxy 仅做流量转发。
|
||||
|
|
|
@ -28,16 +28,16 @@ tags:
|
|||
<!--
|
||||
An agent that runs on each {{< glossary_tooltip text="node" term_id="node" >}} in the cluster. It makes sure that {{< glossary_tooltip text="containers" term_id="container" >}} are running in a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
|
||||
-->
|
||||
一个在集群中每个{{< glossary_tooltip text="节点(node)" term_id="node" >}}上运行的代理。
|
||||
它保证{{< glossary_tooltip text="容器(containers)" term_id="container" >}}都
|
||||
运行在 {{< glossary_tooltip text="Pod" term_id="pod" >}} 中。
|
||||
`kubelet` 会在集群中每个{{< glossary_tooltip text="节点(node)" term_id="node" >}}上运行。
|
||||
它保证{{< glossary_tooltip text="容器(containers)" term_id="container" >}}都运行在
|
||||
{{< glossary_tooltip text="Pod" term_id="pod" >}} 中。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by Kubernetes.
|
||||
-->
|
||||
kubelet 接收一组通过各类机制提供给它的 PodSpecs,确保这些 PodSpecs
|
||||
中描述的容器处于运行状态且健康。
|
||||
kubelet 接收一组通过各类机制提供给它的 PodSpecs,
|
||||
确保这些 PodSpecs 中描述的容器处于运行状态且健康。
|
||||
kubelet 不会管理不是由 Kubernetes 创建的容器。
|
||||
|
||||
|
|
Loading…
Reference in New Issue