Switch language name 'zh' to 'zh-cn'
This is the first step to rename 'zh' to 'zh-cn'. There are several reasons why we rename the language name.
- The upstream docsy theme changed the language name, leading to many warnings during site build;
The side-effect is that the i18n strings are no longer working.
- We believe renaming the language is the right thing to do, because this move can make room for other variants of Chinese language, such as 'zh-tw', 'zh-sg' etc.
There would be several follow-ups to this PR, such as fixing the intra-site links, adding redirects etc.
We will lock up changes to zh/zh-cn pages for the moment, until this one gets in.
This PR is based on commit cdad0a7342.
This commit is contained in:
Qiming Teng
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 附加组件（Add-ons）
|
||||
id: addons
|
||||
date: 2019-12-15
|
||||
full_link: /zh/docs/concepts/cluster-administration/addons/
|
||||
short_description: >
|
||||
扩展 Kubernetes 功能的资源。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Add-ons
|
||||
id: addons
|
||||
date: 2019-12-15
|
||||
full_link: /docs/concepts/cluster-administration/addons/
|
||||
short_description: >
|
||||
Resources that extend the functionality of Kubernetes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
Resources that extend the functionality of Kubernetes.
|
||||
-->
|
||||
扩展 Kubernetes 功能的资源。
|
||||
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
[Installing addons](/docs/concepts/cluster-administration/addons/) explains more about using add-ons with your cluster, and lists some popular add-ons.
|
||||
-->
|
||||
[安装附加组件](/zh/docs/concepts/cluster-administration/addons/) 阐释了更多关于如何在集群内使用附加组件，并列出了一些流行的附加组件。
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 准入控制器（Admission Controller）
|
||||
id: admission-controller
|
||||
date: 2019-06-28
|
||||
full_link: /zh/docs/reference/access-authn-authz/admission-controllers/
|
||||
short_description: >
|
||||
在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
- security
|
||||
---
|
||||
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Admission Controller
|
||||
id: admission-controller
|
||||
date: 2019-06-28
|
||||
full_link: /docs/reference/access-authn-authz/admission-controllers/
|
||||
short_description: >
|
||||
A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
|
||||
-->
|
||||
在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Admission controllers are configurable for the Kubernetes API server and may be “validating”, “mutating”, or
|
||||
both. Any admission controller may reject the request. Mutating controllers may modify the objects they admit;
|
||||
validating controllers may not.
|
||||
|
||||
* [Admission controllers in the Kubernetes documentation](/docs/reference/access-authn-authz/admission-controllers/)
|
||||
-->
|
||||
|
||||
准入控制器可针对 Kubernetes Api 服务器进行配置，可以执行验证，变更或两者都执行。任何准入控制器都可以拒绝访问请求。
|
||||
变更（mutating）控制器可以修改其允许的对象，验证（validating）控制器则不可以。
|
||||
|
||||
* [Kubernetes 文档中的准入控制器](/zh/docs/reference/access-authn-authz/admission-controllers/)
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 亲和性（Affinity）
|
||||
id: affinity
|
||||
date: 2019-01-11
|
||||
full_link: zh/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
|
||||
short_description: >
|
||||
调度程序用于确定在何处放置 Pods（亲和性）的规则
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Affinity
|
||||
id: affinity
|
||||
date: 2019-01-11
|
||||
full_link: /docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
|
||||
short_description: >
|
||||
Rules used by the scheduler to determine where to place pods
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
In Kubernetes, _affinity_ is a set of rules that give hints to the scheduler about where to place pods.
|
||||
-->
|
||||
在 Kubernetes 中，_亲和性（affinity）_是一组规则，它们为调度程序提供在何处放置 Pods 提示信息。
|
||||
<!--more-->
|
||||
<!--
|
||||
There are two kinds of affinity:
|
||||
-->
|
||||
亲和性有两种：
|
||||
<!--
|
||||
* [node affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
|
||||
* [pod-to-pod affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
|
||||
-->
|
||||
* [节点亲和性](/zh/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
|
||||
* [Pod 间亲和性](/zh/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
|
||||
|
||||
<!--
|
||||
The rules are defined using the Kubernetes {{< glossary_tooltip term_id="label" text="labels">}},
|
||||
and {{< glossary_tooltip term_id="selector" text="selectors">}} specified in {{< glossary_tooltip term_id="pod" text="pods" >}},
|
||||
and they can be either required or preferred, depending on how strictly you want the scheduler to enforce them.
|
||||
-->
|
||||
这些规则是使用 Kubernetes {{< glossary_tooltip term_id="label" text="标签">}}（label）
|
||||
和 {{< glossary_tooltip term_id="pod" text="pods" >}} 中指定的
|
||||
{{< glossary_tooltip term_id="selector" text="选择算符">}}定义的，
|
||||
这些规则可以是必需的或首选的，这取决于你希望调度程序执行它们的严格程度。
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: 聚合层（Aggregation Layer）
|
||||
id: aggregation-layer
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
short_description: >
|
||||
聚合层允许你在自己的集群上安装额外的 Kubernetes 风格的 API。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- extension
|
||||
- operation
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Aggregation Layer
|
||||
id: aggregation-layer
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
short_description: >
|
||||
The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- extension
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
<!--
|
||||
The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
|
||||
-->
|
||||
|
||||
聚合层允许你在自己的集群上安装额外的 Kubernetes 风格的 API。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
<!--
|
||||
When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/extend-kubernetes/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
|
||||
-->
|
||||
|
||||
当你配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/zh/docs/tasks/extend-kubernetes/configure-aggregation-layer/)，
|
||||
你就可以在 Kubernetes API 中增加 `APIService` 对象来 "申领（Claim）" 一个 URL 路径。
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: 注解（Annotation）
|
||||
id: annotation
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/annotations/
|
||||
short_description: >
|
||||
注解是以键值对的形式给资源对象附加随机的无法标识的元数据。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Annotation
|
||||
id: annotation
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/annotations
|
||||
short_description: >
|
||||
A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
|
||||
<!--
|
||||
A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
|
||||
-->
|
||||
|
||||
注解是以键值对的形式给资源对象附加随机的无法标识的元数据。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by {{< glossary_tooltip text="labels" term_id="label" >}}. Clients such as tools and libraries can retrieve this metadata.
|
||||
-->
|
||||
|
||||
注解中的元数据可大可小，可以是结构化的也可以是非结构化的，
|
||||
并且能包含{{< glossary_tooltip text="标签" term_id="label" >}}不允许使用的字符。
|
||||
像工具和软件库这样的客户端可以检索这些元数据。
|
||||
|
||||
@@ -0,0 +1,58 @@
|
||||
---
|
||||
title: API 发起的驱逐
|
||||
id: api-eviction
|
||||
date: 2021-04-27
|
||||
full_link: /zh/docs/concepts/scheduling-eviction/pod-eviction/#api-eviction
|
||||
short_description: >
|
||||
API 发起的驱逐是一个先调用 Eviction API 创建驱逐对象，再由该对象体面地中止 Pod 的过程。
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
title: API-initiated eviction
|
||||
id: api-eviction
|
||||
date: 2021-04-27
|
||||
full_link: /docs/concepts/scheduling-eviction/pod-eviction/#api-eviction
|
||||
short_description: >
|
||||
API-initiated eviction is the process by which you use the Eviction API to create an
|
||||
Eviction object that triggers graceful pod termination.
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
API-initiated eviction is the process by which you use the [Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/#create-eviction-pod-v1-core)
|
||||
to create an `Eviction` object that triggers graceful pod termination.
|
||||
-->
|
||||
API 发起的驱逐是一个先调用
|
||||
[Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/#create-eviction-pod-v1-core)
|
||||
创建 `Eviction` 对象，再由该对象体面地中止 Pod 的过程。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can request eviction either by directly calling the Eviction API
|
||||
using a client of the kube-apiserver, like the `kubectl drain` command.
|
||||
When an `Eviction` object is created, the API server terminates the Pod.
|
||||
|
||||
API-initiated evictions respect your configured [`PodDisruptionBudgets`](/docs/tasks/run-application/configure-pdb/)
|
||||
and [`terminationGracePeriodSeconds`](/docs/concepts/workloads/pods/pod-lifecycle#pod-termination).
|
||||
|
||||
API-initiated eviction is not the same as [node-pressure eviction](/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction).
|
||||
-->
|
||||
你可以通过 kube-apiserver 的客户端，比如 `kubectl drain` 这样的命令，直接调用 Eviction API 发起驱逐。
|
||||
当 `Eviction` 对象创建出来之后，该对象将驱动 API 服务器终止选定的Pod。
|
||||
|
||||
API 发起的驱逐取决于你配置的 [`PodDisruptionBudgets`](/zh/docs/tasks/run-application/configure-pdb/)
|
||||
和 [`terminationGracePeriodSeconds`](/zh/docs/concepts/workloads/pods/pod-lifecycle#pod-termination)。
|
||||
|
||||
API 发起的驱逐不同于
|
||||
[节点压力引发的驱逐](/zh/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction)。
|
||||
|
||||
<!--
|
||||
* See [API-initiated eviction](/docs/concepts/scheduling-eviction/api-eviction/) for more information.
|
||||
-->
|
||||
* 有关详细信息，请参阅 [API 发起的驱逐](/zh/docs/concepts/scheduling-eviction/api-eviction/)。
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: API Group
|
||||
id: api-group
|
||||
date: 2019-09-02
|
||||
full_link: /zh/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning
|
||||
short_description: >
|
||||
Kubernetes API 中的一组相关路径
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: API Group
|
||||
id: api-group
|
||||
date: 2019-09-02
|
||||
full_link: /docs/concepts/overview/kubernetes-api/#api-groups-and-versioning
|
||||
short_description: >
|
||||
A set of related paths in the Kubernetes API.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A set of related paths in Kubernetes API.
|
||||
-->
|
||||
Kubernetes API 中的一组相关路径。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can enable or disable each API group by changing the configuration of your API server. You can also disable or enable paths to specific resources. API group makes it easier to extend the Kubernetes API. The API group is specified in a REST path and in the `apiVersion` field of a serialized object.
|
||||
-->
|
||||
通过更改 API server 的配置，可以启用或禁用每个 API Group。
|
||||
你还可以禁用或启用指向特定资源的路径。
|
||||
API group 使扩展 Kubernetes API 更加的容易。
|
||||
API group 在 REST 路径和序列化对象的 `apiVersion` 字段中指定。
|
||||
|
||||
<!--
|
||||
* Read [API Group](/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) for more information.
|
||||
-->
|
||||
* 阅读 [API Group](/zh/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) 了解更多信息。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 应用程序容器（App Container）
|
||||
id: app-container
|
||||
date: 2019-02-12
|
||||
full_link:
|
||||
short_description: >
|
||||
用于运行部分工作负载的容器。与初始化容器比较而言。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: App Container
|
||||
id: app-container
|
||||
date: 2019-02-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A container used to run part of a workload. Compare with init container.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Application containers (or app containers) are the {{< glossary_tooltip text="containers" term_id="container" >}} in a {{< glossary_tooltip text="pod" term_id="pod" >}} that are started after any {{< glossary_tooltip text="init containers" term_id="init-container" >}} have completed.
|
||||
-->
|
||||
应用程序 {{< glossary_tooltip text="容器" term_id="container" >}} （或 app 容器）在 {{< glossary_tooltip text="pod" term_id="pod" >}} 中，在 {{< glossary_tooltip text="初始化容器" term_id="init-container" >}} 启动完毕后才开始启动。
|
||||
|
||||
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
An init container lets you separate initialization details that are important for the overall
|
||||
{{< glossary_tooltip text="workload" term_id="workload" >}}, and that don't need to keep running
|
||||
once the application container has started.
|
||||
If a pod doesn't have any init containers configured, all the containers in that pod are app containers.
|
||||
-->
|
||||
|
||||
初始化容器使你可以分离对于{{< glossary_tooltip text="工作负载" term_id="workload" >}}
|
||||
整体而言很重要的初始化细节，并且一旦应用容器启动，它不需要继续运行。
|
||||
如果 pod 没有配置任何初始化容器，则该 pod 中的所有容器都是应用程序容器。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 应用架构师（Application Architect）
|
||||
id: application-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
应用架构师是负责应用高级设计的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Application Architect
|
||||
id: application-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person responsible for the high-level design of an application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person responsible for the high-level design of an application.
|
||||
-->
|
||||
应用架构师是负责应用高级设计的人。
|
||||
|
||||
|
||||
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way. Surrounding components include databases, logging infrastructure, and other microservices.
|
||||
-->
|
||||
|
||||
应用架构师确保应用的实现允许它和周边组件进行可扩展的、可持续的交互。
|
||||
周边组件包括数据库、日志基础设施和其他微服务。
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 应用开发者（Application Developer）
|
||||
id: application-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
编写可以在 Kubernetes 集群上运行的应用的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Application Developer
|
||||
id: application-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who writes an application that runs in a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A person who writes an application that runs in a Kubernetes cluster.
|
||||
-->
|
||||
|
||||
编写可以在 Kubernetes 集群上运行的应用的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
An application developer focuses on one part of an application. The scale of their focus may vary significantly in size.
|
||||
-->
|
||||
|
||||
应用开发者专注于应用的某一部分。他们工作范围的大小有明显的差异。
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: 应用（Applications）
|
||||
id: applications
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
各种容器化应用运行所在的层。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Applications
|
||||
id: applications
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The layer where various containerized applications run.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
The layer where various containerized applications run.
|
||||
-->
|
||||
各种容器化应用运行所在的层。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 批准者（Approver）
|
||||
id: approver
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
可以审核并批准 Kubernetes 代码贡献的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Approver
|
||||
id: approver
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who can review and approve Kubernetes code contributions.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who can review and approve Kubernetes code contributions.
|
||||
-->
|
||||
可以审核并批准 Kubernetes 代码贡献的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
While code review is focused on code quality and correctness, approval is focused on the holistic acceptance of a contribution. Holistic acceptance includes backwards/forwards compatibility, adhering to API and flag conventions, subtle performance and correctness issues, interactions with other parts of the system, and others. Approver status is scoped to a part of the codebase. Approvers were previously referred to as maintainers.
|
||||
-->
|
||||
|
||||
代码审核的重点是代码质量和正确性，而批准的重点是对贡献的整体接受。
|
||||
整体接受包括向后/向前兼容性、遵守 API 和参数约定、细微的性能和正确性问题、与系统其他部分的交互等。
|
||||
批准者状态的作用域是代码库的一部分。审批者以前被称为维护者。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: cAdvisor
|
||||
id: cadvisor
|
||||
date: 2021-12-09
|
||||
full_link: https://github.com/google/cadvisor/
|
||||
short_description: >
|
||||
帮助理解容器的资源用量与性能特征的工具
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
title: cAdvisor
|
||||
id: cadvisor
|
||||
date: 2021-12-09
|
||||
full_link: https://github.com/google/cadvisor/
|
||||
short_description: >
|
||||
Tool that provides understanding of the resource usage and performance characteristics for containers
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
-->
|
||||
|
||||
<!--
|
||||
cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running {{< glossary_tooltip text="containers" term_id="container" >}}.
|
||||
-->
|
||||
cAdvisor (Container Advisor) 为容器用户提供对其运行中的{{< glossary_tooltip text="容器" term_id="container" >}}
|
||||
的资源用量和性能特征的知识。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide.
|
||||
-->
|
||||
cAdvisor 是一个守护进程，负责收集、聚合、处理并输出运行中容器的信息。
|
||||
具体而言，针对每个容器，该进程记录容器的资源隔离参数、历史资源用量、
|
||||
完整历史资源用量和网络统计的直方图。这些数据可以按容器或按机器层面输出。
|
||||
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 证书（Certificate）
|
||||
id: certificate
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
short_description: >
|
||||
证书是个安全加密文件，用来确认对 Kubernetes 集群访问的合法性。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Certificate
|
||||
id: certificate
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
short_description: >
|
||||
A cryptographically secure file used to validate access to the Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A cryptographically secure file used to validate access to the Kubernetes cluster.
|
||||
-->
|
||||
|
||||
证书是个安全加密文件，用来确认对 Kubernetes 集群访问的合法性。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Certificates enable applications within a Kubernetes cluster to access the Kubernetes API securely. Certificates validate that clients are allowed to access the API.
|
||||
-->
|
||||
|
||||
证书可以让 Kubernetes 集群中运行的应用程序安全的访问 Kubernetes API。证书可以确认客户端是否被允许访问 API。
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 控制组（cgroup）
|
||||
id: cgroup
|
||||
date: 2019-06-25
|
||||
full_link:
|
||||
short_description: >
|
||||
一组具有可选资源隔离、审计和限制的 Linux 进程。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: cgroup (control group)
|
||||
id: cgroup
|
||||
date: 2019-06-25
|
||||
full_link:
|
||||
short_description: >
|
||||
A group of Linux processes with optional resource isolation, accounting and limits.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A group of Linux processes with optional resource isolation, accounting and limits.
|
||||
-->
|
||||
一组具有可选资源隔离、审计和限制的 Linux 进程。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
cgroup is a Linux kernel feature that limits, accounts for, and isolates the resource usage (CPU, memory, disk I/O, network) for a collection of processes.
|
||||
-->
|
||||
|
||||
Cgroup 是一个 Linux 内核特性，对一组进程的资源使用（CPU、内存、磁盘 I/O 和网络等）进行限制、审计和隔离。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: CIDR
|
||||
id: cidr
|
||||
date: 2019-11-12
|
||||
full_link:
|
||||
short_description: >
|
||||
CIDR 是一种描述 IP 地址块的符号，被广泛使用于各种网络配置中。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CIDR
|
||||
id: cidr
|
||||
date: 2019-11-12
|
||||
full_link:
|
||||
short_description: >
|
||||
CIDR is a notation for describing blocks of IP addresses and is used heavily in various networking configurations.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
CIDR (Classless Inter-Domain Routing) is a notation for describing blocks of IP addresses and is used heavily in various networking configurations.
|
||||
-->
|
||||
CIDR (无类域间路由) 是一种描述 IP 地址块的符号，被广泛使用于各种网络配置中。
|
||||
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
In the context of Kubernetes, each {{< glossary_tooltip text="Node" term_id="node" >}} is assigned a range of IP addresses through the start address and a subnet mask using CIDR. This allows Nodes to assign each {{< glossary_tooltip text="Pod" term_id="pod" >}} a unique IP address. Although originally a concept for IPv4, CIDR has also been expanded to include IPv6.
|
||||
-->
|
||||
在 Kubernetes 的上下文中，每个{{< glossary_tooltip text="节点" term_id="node" >}}
|
||||
以 CIDR 形式（含起始地址和子网掩码）获得一个 IP 地址段，
|
||||
从而能够为每个 {{< glossary_tooltip text="Pod" term_id="pod" >}} 分配一个独一无二的 IP 地址。
|
||||
虽然其概念最初源自 IPv4，CIDR 已经被扩展为涵盖 IPv6。
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 贡献者许可协议（CLA）
|
||||
id: cla
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/CLA.md
|
||||
short_description: >
|
||||
贡献者对他们在开源项目中所贡献的代码的授权许可条款。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CLA (Contributor License Agreement)
|
||||
id: cla
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/CLA.md
|
||||
short_description: >
|
||||
Terms under which a contributor grants a license to an open source project for their contributions.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Terms under which a {{< glossary_tooltip text="contributor" term_id="contributor" >}} grants a license to an open source project for their contributions.
|
||||
-->
|
||||
{{< glossary_tooltip text="贡献者" term_id="contributor" >}}对他们在开源项目中所贡献的代码的授权许可条款。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
CLAs help resolve legal disputes involving contributed material and intellectual property (IP).
|
||||
-->
|
||||
|
||||
CLA 对解决贡献者在开源社区所贡献的资料和智力资产（IP）导致的法律纠纷很有帮助。
|
||||
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: 云控制器管理器（Cloud Controller Manager）
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/cloud-controller/
|
||||
short_description: >
|
||||
将 Kubernetes 与第三方云提供商进行集成的控制面组件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- architecture
|
||||
- operation
|
||||
---
|
||||
<!--
|
||||
title: Cloud Controller Manager
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/architecture/cloud-controller/
|
||||
short_description: >
|
||||
Control plane component that integrates Kubernetes with third-party cloud providers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- architecture
|
||||
- operation
|
||||
-->
|
||||
|
||||
<!--
|
||||
A Kubernetes {{< glossary_tooltip text="control plane" term_id="control-plane" >}} component
|
||||
that embeds cloud-specific control logic. The cloud controller manager lets you link your
|
||||
cluster into your cloud provider's API, and separates out the components that interact
|
||||
with that cloud platform from components that only interact with your cluster.
|
||||
-->
|
||||
`cloud-controller-manager` 是指嵌入特定云的控制逻辑之
|
||||
{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}组件。
|
||||
`cloud-controller-manager` 允许你将你的集群连接到云提供商的 API 之上，
|
||||
并将与该云平台交互的组件同与你的集群交互的组件分离开来。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
By decoupling the interoperability logic between Kubernetes and the underlying cloud
|
||||
infrastructure, the cloud-controller-manager component enables cloud providers to release
|
||||
features at a different pace compared to the main Kubernetes project.
|
||||
-->
|
||||
通过分离 Kubernetes 和底层云基础设置之间的互操作性逻辑，
|
||||
`cloud-controller-manager` 组件使云提供商能够以不同于 Kubernetes 主项目的
|
||||
步调发布新特征。
|
||||
@@ -0,0 +1,65 @@
|
||||
---
|
||||
title: 云供应商（Cloud Provider）
|
||||
id: cloud-provider
|
||||
date: 2018-04-12
|
||||
short_description: >
|
||||
一个提供云计算平台的组织。
|
||||
|
||||
aka:
|
||||
- 云服务供应商（Cloud Service Provider）
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Provider
|
||||
id: cloud-provider
|
||||
date: 2018-04-12
|
||||
short_description: >
|
||||
An organization that offers a cloud computing platform.
|
||||
|
||||
aka:
|
||||
- Cloud Service Provider
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A business or other organization that offers a cloud computing platform.
|
||||
-->
|
||||
一个提供云计算平台的商业机构或其他组织。
|
||||
|
||||
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Cloud providers, sometimes called Cloud Service Providers (CSPs), offer
|
||||
cloud computing platforms or services.
|
||||
|
||||
Many cloud providers offer managed infrastructure (also called
|
||||
Infrastructure as a Service or IaaS).
|
||||
With managed infrastructure the cloud provider is responsible for
|
||||
servers, storage, and networking while you manage layers on top of that
|
||||
such as running a Kubernetes cluster.
|
||||
|
||||
You can also find Kubernetes as a managed service; sometimes called
|
||||
Platform as a Service, or PaaS. With managed Kubernetes, your
|
||||
cloud provider is responsible for the Kubernetes control plane as well
|
||||
as the {{< glossary_tooltip term_id="node" text="nodes" >}} and the
|
||||
infrastructure they rely on: networking, storage, and possibly other
|
||||
elements such as load balancers.
|
||||
-->
|
||||
云供应商，有时也称作云服务供应商（CSPs）提供云计算平台或服务。
|
||||
|
||||
很多云供应商提供托管的基础设施（也称作基础设施即服务或 IaaS）。
|
||||
针对托管的基础设施，云供应商负责服务器、存储和网络，而用户（你）
|
||||
负责管理其上运行的各层软件，例如运行一个 Kubernetes 集群。
|
||||
|
||||
你也会看到 Kubernetes 被作为托管服务提供；有时也称作平台即服务或 PaaS。
|
||||
针对托管的 Kubernetes，你的云供应商负责 Kubernetes 的控制面以及
|
||||
{{< glossary_tooltip term_id="node" text="节点" >}} 及他们所依赖的基础设施：
|
||||
网络、存储以及其他一些诸如负载均衡器之类的元素。
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: 集群架构师（Cluster Architect）
|
||||
id: cluster-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
集群架构师负责设计集群的基础设施，可能包含一个或多个 Kubernetes 集群。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Architect
|
||||
id: cluster-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who designs infrastructure that involves one or more Kubernetes clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
集群架构师负责设计集群的基础设施，可能包含一个或多个 Kubernetes 集群。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Cluster architects are concerned with best practices for distributed systems, for example: high availability and security.
|
||||
-->
|
||||
|
||||
集群架构师要具备分布式系统的最佳实践经验，例如：高可用性和安全性。
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: 集群基础设施（Cluster Infrastructure）
|
||||
id: cluster-infrastructure
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
基础设施层提供并维护虚拟机、网络、安全组及其他资源。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Cluster Infrastructure
|
||||
id: cluster-infrastructure
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The infrastructure layer provides and maintains VMs, networking, security groups and others.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
-->
|
||||
<!--
|
||||
The infrastructure layer provides and maintains VMs, networking, security groups and others.
|
||||
-->
|
||||
基础设施层提供并维护虚拟机、网络、安全组及其他资源。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 集群操作（Cluster Operations）
|
||||
id: cluster-operations
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
管理 Kubernetes 集群所涉及的相关工作。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Operations
|
||||
id: cluster-operations
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The work involved in managing a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The work involved in managing a Kubernetes cluster: managing
|
||||
day-to-day operations, and co-ordinating upgrades.
|
||||
-->
|
||||
Kubernetes 管理相关工作包括：日常管理操作和协调升级。
|
||||
|
||||
<!--
|
||||
Examples of cluster operations work include: deploying new Nodes to
|
||||
scale the cluster; performing software upgrades; implementing security
|
||||
controls; adding or removing storage; configuring cluster networking;
|
||||
managing cluster-wide observability; and responding to events.
|
||||
-->
|
||||
集群操作工作的示例包括：部署新节点来扩容集群；执行软件升级；实施安全控制；
|
||||
添加或删除存储；配置集群网络；管理集群范围的可观测性；响应集群事件。
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: 集群操作者（Cluster Operator）
|
||||
id: cluster-operator
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
配置、控制、监控集群的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Operator
|
||||
id: cluster-operator
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who configures, controls, and monitors clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who configures, controls, and monitors clusters.
|
||||
-->
|
||||
配置、控制、监控集群的人。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Their primary responsibility is keeping a cluster up and running, which may involve periodic maintenance activities or upgrades.<br>
|
||||
|
||||
|
||||
**NOTE:** Cluster operators are different from the [Operator pattern](https://www.openshift.com/learn/topics/operators) that extends the Kubernetes API.
|
||||
-->
|
||||
|
||||
他们的主要责任是保持集群正常运行，可能需要进行周期性的维护和升级活动。<br>
|
||||
|
||||
**注意：** 集群操作者不同于[操作者模式（Operator Pattern）](https://www.openshift.com/learn/topics/operators)，操作者模式是用来扩展 Kubernetes API 的。
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 集群（Cluster）
|
||||
id: cluster
|
||||
date: 2019-06-15
|
||||
full_link:
|
||||
short_description: >
|
||||
集群由一组被称作节点的机器组成。这些节点上运行 Kubernetes 所管理的容器化应用。集群具有至少一个工作节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster
|
||||
id: cluster
|
||||
date: 2019-06-15
|
||||
full_link:
|
||||
short_description: >
|
||||
A set of worker machines, called nodes, that run containerized applications. Every cluster has at least one worker node.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
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.
|
||||
-->
|
||||
集群是由一组被称作{{< glossary_tooltip text="节点（node）" term_id="node" >}}的机器组成，
|
||||
这些节点上会运行由 Kubernetes 所管理的容器化应用。
|
||||
且每个集群至少有一个工作节点。
|
||||
<!--more-->
|
||||
<!--
|
||||
The worker node(s) host the {{< glossary_tooltip text="Pods" term_id="pod" >}} that are
|
||||
the components of the application workload. The
|
||||
{{< glossary_tooltip text="control plane" term_id="control-plane" >}} manages the worker
|
||||
nodes and the Pods in the cluster. In production environments, the control plane usually
|
||||
runs across multiple computers and a cluster usually runs multiple nodes, providing
|
||||
fault-tolerance and high availability.
|
||||
-->
|
||||
工作节点会托管所谓的 Pods，而 Pod 就是作为应用负载的组件。
|
||||
控制平面管理集群中的工作节点和 Pods。
|
||||
为集群提供故障转移和高可用性，
|
||||
这些控制平面一般跨多主机运行，而集群也会跨多个节点运行。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 云原生计算基金会（CNCF）
|
||||
id: cncf
|
||||
date: 2019-05-26
|
||||
full_link: https://cncf.io/
|
||||
short_description: >
|
||||
云原生计算基金会
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
云原生计算基金会（CNCF）建立了可持续的生态系统，并在围绕着 [项目](https://www.cncf.io/projects/) 建立一个社区，将容器编排微服务架构的一部分。
|
||||
|
||||
Kubernetes 是一个云原生计算基金会项目.
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Native Computing Foundation (CNCF)
|
||||
id: cncf
|
||||
date: 2019-05-26
|
||||
full_link: https://cncf.io/
|
||||
short_description: >
|
||||
Cloud Native Computing Foundation
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
The Cloud Native Computing Foundation (CNCF) builds sustainable ecosystems and
|
||||
fosters a community around [projects](https://www.cncf.io/projects/) that
|
||||
orchestrate containers as part of a microservices architecture.
|
||||
|
||||
Kubernetes is a CNCF project.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The CNCF is a sub-foundation of [the Linux Foundation](https://www.linuxfoundation.org/).
|
||||
Its mission is to make cloud native computing ubiquitous.
|
||||
-->
|
||||
云原生计算基金会（CNCF）是 [Linux 基金会](https://www.linuxfoundation.org/) 的下属基金会。它的使命是让云原生计算无处不在。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 容器网络接口（CNI）
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container network interface (CNI)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
-->
|
||||
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* For information on Kubernetes and CNI refer to [this](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
-->
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 代码贡献者（Code Contributor）
|
||||
id: code-contributor
|
||||
date: 2018-04-12
|
||||
full_link: /docs/community/devel/
|
||||
short_description: >
|
||||
为 Kubernetes 开源代码库开发并贡献代码的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Code Contributor
|
||||
id: code-contributor
|
||||
date: 2018-04-12
|
||||
full_link: /docs/community/devel/
|
||||
short_description: >
|
||||
A person who develops and contributes code to the Kubernetes open source codebase.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who develops and contributes code to the Kubernetes open source codebase.
|
||||
-->
|
||||
|
||||
为 Kubernetes 开源代码库开发并贡献代码的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
They are also an active {{< glossary_tooltip text="community member" term_id="member" >}} who participates in one or more {{< glossary_tooltip text="Special Interest Groups (SIGs)" term_id="sig" >}}.
|
||||
-->
|
||||
|
||||
代码贡献者也是加入一个或多个 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}} 的活跃的 {{< glossary_tooltip text="社区成员" term_id="member" >}}。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
short_description: >
|
||||
ConfigMap 是一种 API 对象，用来将非机密性的数据保存到键值对中。使用时可以用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/configuration/configmap/
|
||||
short_description: >
|
||||
An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or configuration files in a volume.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object used to store non-confidential data in key-value pairs.
|
||||
{{< glossary_tooltip text="Pods" term_id="pod" >}} can consume ConfigMaps as
|
||||
environment variables, command-line arguments, or as configuration files in a
|
||||
{{< glossary_tooltip text="volume" term_id="volume" >}}.
|
||||
-->
|
||||
|
||||
ConfigMap 是一种 API 对象，用来将非机密性的数据保存到键值对中。使用时， {{< glossary_tooltip text="Pods" term_id="pod" >}} 可以将其用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A ConfigMap allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="image" >}}, so that your applications are easily portable.
|
||||
-->
|
||||
|
||||
ConfigMap 将你的环境配置信息和 {{< glossary_tooltip text="容器镜像" term_id="image" >}} 解耦，便于应用配置的修改。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 容器环境变量（Container Environment Variables）
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/containers/container-environment/
|
||||
short_description: >
|
||||
容器环境变量提供了 name=value 形式的、运行容器化应用所必须的一些重要信息。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container Environment Variables
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/containers/container-environment/
|
||||
short_description: >
|
||||
Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Container environment variables are name=value pairs that provide useful information into containers running in a {{< glossary_tooltip text="pod" term_id="pod" >}}
|
||||
-->
|
||||
|
||||
容器环境变量提供了 name=value 形式的、在 {{< glossary_tooltip text="pod" term_id="pod" >}} 中运行的容器所必须的一些重要信息。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Container environment variables provide information that is required by the running containerized applications along with information about important resources to the {{< glossary_tooltip text="containers" term_id="container" >}}. For example, file system details, information about the container itself, and other cluster resources such as service endpoints.
|
||||
-->
|
||||
|
||||
容器环境变量为运行中的容器化应用提供必要的信息，同时还提供与 {{< glossary_tooltip text="容器" term_id="container" >}} 重要资源相关的其他信息，例如：文件系统信息、容器自身的信息以及其他像服务端点（Service endpoints）这样的集群资源信息。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 容器生命周期钩子（Container Lifecycle Hooks）
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/containers/container-lifecycle-hooks/
|
||||
short_description: >
|
||||
生命周期钩子暴露容器管理生命周期中的事件，允许用户在事件发生时运行代码。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Container Lifecycle Hooks
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/containers/container-lifecycle-hooks/
|
||||
short_description: >
|
||||
The lifecycle hooks expose events in the container management lifecycle and let the user run code when the events occur.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
生命周期钩子暴露{{< glossary_tooltip text="容器" term_id="container" >}}管理生命周期中的事件，允许用户在事件发生时运行代码。
|
||||
<!--
|
||||
The lifecycle hooks expose events in the {{< glossary_tooltip text="Container" term_id="container" >}}container management lifecycle and let the user run code when the events occur.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
针对容器暴露了两个钩子：PostStart 在容器创建之后立即执行，PreStop 在容器停止之前立即阻塞并被调用。
|
||||
<!--
|
||||
Two hooks are exposed to Containers: PostStart which executes immediately after a container is created and PreStop which is blocking and is called immediately before a container is terminated.
|
||||
-->
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 容器运行时接口
|
||||
id: container-runtime-interface
|
||||
date: 2021-11-24
|
||||
full_link: /zh/docs/concepts/architecture/cri
|
||||
short_description: >
|
||||
kubelet 和容器运行时之间通信的主要协议。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- cri
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Container Runtime Interface
|
||||
id: container-runtime-interface
|
||||
date: 2021-11-24
|
||||
full_link: /docs/concepts/architecture/cri
|
||||
short_description: >
|
||||
The main protocol for the communication between the kubelet and Container Runtime.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- cri
|
||||
-->
|
||||
|
||||
<!-- The main protocol for the communication between the kubelet and Container Runtime. -->
|
||||
kubelet 和容器运行时之间通信的主要协议。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The Kubernetes Container Runtime Interface (CRI) defines the main
|
||||
[gRPC](https://grpc.io) protocol for the communication between the
|
||||
[cluster components](/docs/concepts/overview/components/#node-components)
|
||||
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and
|
||||
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
|
||||
-->
|
||||
Kubernetes 容器运行时接口（CRI）定义了主要 [gRPC](https://grpc.io) 协议，
|
||||
用于[集群组件](/zh/docs/concepts/overview/components/#node-components)
|
||||
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 和
|
||||
{{< glossary_tooltip text="容器运行时" term_id="container-runtime" >}}。
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: 容器运行时（Container Runtime）
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /zh/docs/setup/production-environment/container-runtimes
|
||||
short_description: >
|
||||
容器运行时是负责运行容器的软件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Container Runtime
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /docs/setup/production-environment/container-runtimes
|
||||
short_description: >
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
-->
|
||||
容器运行环境是负责运行容器的软件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes supports container runtimes such sa
|
||||
{{< glossary_tooltip term_id="docker">}},
|
||||
{{< glossary_tooltip term_id="containerd" >}}, {{< glossary_tooltip term_id="cri-o" >}},
|
||||
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 支持许多容器运行环境，例如
|
||||
{{< glossary_tooltip term_id="docker">}}、
|
||||
{{< 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)
|
||||
的其他任何实现。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 容器（Container）
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
short_description: >
|
||||
容器是可移植、可执行的轻量级的镜像，镜像中包含软件及其相关依赖。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Container
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/containers/
|
||||
short_description: >
|
||||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
-->
|
||||
|
||||
<!--
|
||||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
-->
|
||||
容器是可移植、可执行的轻量级的镜像，包含其中的软件及其相关依赖。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling.
|
||||
-->
|
||||
容器使应用和底层的主机基础设施解耦，降低了应用在不同云环境或者操作系统上的部署难度，便于应用扩展。
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: containerd
|
||||
id: containerd
|
||||
date: 2019-05-14
|
||||
full_link: https://containerd.io/docs/
|
||||
short_description: >
|
||||
强调简单性、健壮性和可移植性的一种容器运行时
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: containerd
|
||||
id: containerd
|
||||
date: 2019-05-14
|
||||
full_link: https://containerd.io/docs/
|
||||
short_description: >
|
||||
A container runtime with an emphasis on simplicity, robustness and portability
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
强调简单性、健壮性和可移植性的一种容器运行时
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
containerd is a {{< glossary_tooltip text="container" term_id="container" >}} runtime
|
||||
that runs as a daemon on Linux or Windows. containerd takes care of fetching and
|
||||
storing container images, executing containers, providing network access, and more.
|
||||
-->
|
||||
|
||||
containerd 是一种{{< glossary_tooltip text="容器" term_id="container" >}}运行时，能在 Linux 或者 Windows 后台运行。
|
||||
containerd 能取回、存储容器镜像，执行容器实例，提供网络访问等。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 贡献者（Contributor）
|
||||
id: contributor
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Contributor
|
||||
id: contributor
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
-->
|
||||
|
||||
<!--
|
||||
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
|
||||
-->
|
||||
|
||||
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Contributions include pull requests (PRs), issues, feedback, {{< glossary_tooltip text="special interest groups (SIG)" term_id="sig" >}} participation, or organizing community events.
|
||||
-->
|
||||
|
||||
贡献形式包括提交拉取请求（PRs）、问题报告（Issues）、反馈、参与{{< glossary_tooltip text="特别兴趣小组（SIG）" term_id="sig" >}}或者组织社区活动等等。
|
||||
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: 控制平面（Control Plane）
|
||||
id: control-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
控制平面是指容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
<!--
|
||||
title: Control Plane
|
||||
id: control-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
|
||||
-->
|
||||
控制平面（Control Plane）是指容器编排层，它暴露 API 和接口来定义、
|
||||
部署容器和管理容器的生命周期。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
This layer is composed by many different components, such as (but not restricted to):
|
||||
|
||||
* {{< glossary_tooltip text="etcd" term_id="etcd" >}}
|
||||
* {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}
|
||||
* {{< glossary_tooltip text="Scheduler" term_id="kube-scheduler" >}}
|
||||
* {{< glossary_tooltip text="Controller Manager" term_id="kube-controller-manager" >}}
|
||||
* {{< glossary_tooltip text="Cloud Controller Manager" term_id="cloud-controller-manager" >}}
|
||||
|
||||
These components can be run as traditional operating system services (daemons) or as containers. The hosts running these components were historically called {{< glossary_tooltip text="masters" term_id="master" >}}.
|
||||
-->
|
||||
这个编排层是由多个不同的组件组成，例如以下（但不限于）几种：
|
||||
|
||||
* {{< glossary_tooltip text="etcd" term_id="etcd" >}}
|
||||
* {{< glossary_tooltip text="API 服务器" term_id="kube-apiserver" >}}
|
||||
* {{< glossary_tooltip text="调度器" term_id="kube-scheduler" >}}
|
||||
* {{< glossary_tooltip text="控制器管理器" term_id="kube-controller-manager" >}}
|
||||
* {{< glossary_tooltip text="云控制器管理器" term_id="cloud-controller-manager" >}}
|
||||
|
||||
这些组件可以以传统的系统服务运行也可以以容器的形式运行.运行这些组件的主机过去称为 master 节点。
|
||||
@@ -0,0 +1,64 @@
|
||||
---
|
||||
title: 控制器（Controller）
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/controller/
|
||||
short_description: >
|
||||
控制器通过 apiserver 监控集群的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Controller
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/architecture/controller/
|
||||
short_description: >
|
||||
A control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
In Kubernetes, controllers are control loops that watch the state of your
|
||||
{{< glossary_tooltip term_id="cluster" text="cluster">}}, then make or request
|
||||
changes where needed.
|
||||
Each controller tries to move the current cluster state closer to the desired
|
||||
state.
|
||||
-->
|
||||
|
||||
在 Kubernetes 中，控制器通过监控{{< glossary_tooltip text="集群" term_id="cluster" >}}
|
||||
的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
<!--
|
||||
Controllers watch the shared state of your cluster through the
|
||||
{{< glossary_tooltip text="apiserver" term_id="kube-apiserver" >}} (part of the
|
||||
{{< glossary_tooltip term_id="control-plane" >}}).
|
||||
-->
|
||||
控制器（{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的一部分）
|
||||
通过 {{< glossary_tooltip text="apiserver" term_id="kube-apiserver" >}} 监控你的集群中的公共状态。
|
||||
|
||||
<!--
|
||||
Some controllers also run inside the control plane, providing control loops that
|
||||
are core to Kubernetes' operations. For example: the deployment controller, the
|
||||
daemonset controller, the namespace controller, and the persistent volume
|
||||
controller (and others) all run within the
|
||||
{{< glossary_tooltip term_id="kube-controller-manager" >}}.
|
||||
-->
|
||||
其中一些控制器是运行在控制平面内部的，对 Kubernetes 来说，他们提供核心控制操作。
|
||||
比如：部署控制器（deployment controller）、守护控制器（daemonset controller）、
|
||||
命名空间控制器（namespace controller）、持久化数据卷控制器（persistent volume
|
||||
controller）（等）都是运行在 {{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}} 中的。
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/#what-is-cri-o
|
||||
short_description: >
|
||||
专用于 Kubernetes 的轻量级容器运行时软件
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/#what-is-cri-o
|
||||
short_description: >
|
||||
A lightweight container runtime specifically for Kubernetes
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
-->
|
||||
<!--
|
||||
A tool that lets you use OCI container runtimes with Kubernetes CRI.
|
||||
-->
|
||||
该工具可让你通过 Kubernetes CRI 使用 OCI 容器运行时。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
CRI-O is an implementation of the {{< glossary_tooltip term_id="cri" >}}
|
||||
to enable using {{< glossary_tooltip text="container" term_id="container" >}}
|
||||
runtimes that are compatible with the Open Container Initiative (OCI)
|
||||
[runtime spec](https://www.github.com/opencontainers/runtime-spec).
|
||||
-->
|
||||
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" >}}。
|
||||
|
||||
<!--
|
||||
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="Pods" term_id="pod" >}}，
|
||||
并从远程容器仓库获取 OCI 容器镜像。
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 容器运行时接口（CRI）
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /zh/docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
一组与 kubelet 集成的容器运行时 API
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
容器运行时接口 (CRI) 是一组与节点上 kubelet 集成的容器运行时 API
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container runtime interface (CRI)
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
An API for container runtimes to integrate with kubelet
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
The container runtime interface (CRI) is an API for container runtimes
|
||||
to integrate with kubelet on a node.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
For more information, see the [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API and specifications.
|
||||
-->
|
||||
|
||||
更多信息， 请参考 [容器运行时接口](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API 与规格。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 周期调度任务（CronJob）
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
周期调度的任务（作业）。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CronJob
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
A repeating task (a Job) that runs on a regular schedule.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/job/) that runs on a periodic schedule.
|
||||
-->
|
||||
|
||||
管理定期运行的 [任务](/zh/docs/concepts/workloads/controllers/job/)。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Similar to a line in a *crontab* file, a Cronjob object specifies a schedule using the [Cron](https://en.wikipedia.org/wiki/Cron) format.
|
||||
-->
|
||||
|
||||
Cronjob 对象类似 *crontab* 文件中的一行命令，它声明了一个遵循 [Cron](https://en.wikipedia.org/wiki/Cron) 格式的调度任务。
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: 容器存储接口（Container Storage Interface，CSI）
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
容器存储接口 （CSI）定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container Storage Interface (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
-->
|
||||
|
||||
容器存储接口 （CSI） 定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
CSI allows vendors to create custom storage plugins for Kubernetes without adding them to the Kubernetes repository (out-of-tree plugins). To use a CSI driver from a storage provider, you must first [deploy it to your cluster](https://kubernetes-csi.github.io/docs/deploying.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver.
|
||||
|
||||
* [CSI in the Kubernetes documentation](/docs/concepts/storage/volumes/#csi)
|
||||
* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html)
|
||||
-->
|
||||
|
||||
CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件，
|
||||
而无需将这些插件的代码添加到 Kubernetes 代码仓库（外部插件）。
|
||||
要使用某个存储提供商的 CSI 驱动，你首先要
|
||||
[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/deploying.html)。
|
||||
然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/zh/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/drivers.html)
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
||||
short_description: >
|
||||
通过定制化的代码给你的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
||||
Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
|
||||
-->
|
||||
|
||||
通过定制化的代码给你的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs.
|
||||
-->
|
||||
|
||||
当 Kubernetes 公开支持的 API 资源不能满足你的需要时，
|
||||
定制资源对象（Custom Resource Definitions）让你可以在你的环境上扩展 Kubernetes API。
|
||||
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/daemonset/
|
||||
short_description: >
|
||||
确保 Pod 的副本在集群中的一组节点上运行。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/daemonset
|
||||
short_description: >
|
||||
Ensures a copy of a Pod is running across a set of nodes in a cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Ensures a copy of a {{< glossary_tooltip text="Pod" term_id="pod" >}} is running across a set of nodes in a {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
|
||||
-->
|
||||
确保 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的副本在{{< glossary_tooltip text="集群" term_id="cluster" >}}中的一组节点上运行。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {{< glossary_tooltip term_id="node" >}}.
|
||||
-->
|
||||
|
||||
用来部署系统守护进程，例如日志搜集和监控代理，这些进程通常必须运行在每个{{< glossary_tooltip text="节点" term_id="node" >}}上。
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: 数据平面（Data Plane）
|
||||
id: data-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
提供诸如 CPU，内存，网络和存储的能力，以便容器可以运行并连接到网络。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
提供诸如 CPU，内存，网络和存储的能力，以便容器可以运行并连接到网络。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Data Plane
|
||||
id: data-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The layer that provides capacity such as CPU, memory, network, and storage so that the containers can run and connect to a network.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
The layer that provides capacity such as CPU, memory, network, and storage so that the containers can run and connect to a network.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
Deployment 是管理应用副本的 API 对象。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
Manages a replicated application on your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that manages a replicated application, typically by running Pods with no local state.
|
||||
-->
|
||||
|
||||
Deployment 是管理应用副本的 API 对象，通常通过运行没有本地状态的Pods来实现。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Each replica is represented by a {{< glossary_tooltip term_id="pod" >}}, and the Pods are distributed among the
|
||||
{{< glossary_tooltip text="nodes" term_id="node" >}} of a cluster.
|
||||
For workloads that do require local state, consider using a {{< glossary_tooltip term_id="StatefulSet" >}}.
|
||||
-->
|
||||
|
||||
应用的每个副本就是一个 {{< glossary_tooltip text="Pod" term_id="pod" >}}，
|
||||
并且这些 Pod 会分散运行在集群的{{< glossary_tooltip text="节点" term_id="node" >}}上。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 开发者（Developer）
|
||||
id: developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
指的是：应用开发者、代码贡献者、或平台开发者。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Developer (disambiguation)
|
||||
id: developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: Application Developer, Code Contributor, or Platform Developer.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
指的是：{{< glossary_tooltip text="应用开发者" term_id="application-developer" >}}、
|
||||
{{< glossary_tooltip text="代码贡献者" term_id="code-contributor" >}}、
|
||||
或{{< glossary_tooltip text="平台开发者" term_id="platform-developer" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
This overloaded term may have different meanings depending on the context
|
||||
-->
|
||||
|
||||
根据上下文的不同，“开发者”这个被多处使用的词条会有不同的含义。
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: 设备插件（Device Plugin）
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
一种软件扩展，可以使 Pod 访问由特定厂商初始化或者安装的设备。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Device Plugin
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
Software extensions to let Pods access devices that need vendor-specific initialization or setup
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Device plugins run on worker
|
||||
{{< glossary_tooltip term_id="node" text="Nodes">}} and provide
|
||||
{{< glossary_tooltip term_id="pod" text="Pods ">}} with access to resources,
|
||||
such as local hardware, that require vendor-specific initialization or setup
|
||||
steps.
|
||||
-->
|
||||
设备插件工作在节点主机上，给 {{< glossary_tooltip term_id="pod" text="Pods ">}} 提供访问资源的权限，比如特定厂商初始化或者安装的本地硬件。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Device plugins advertise resources to the
|
||||
{{< glossary_tooltip term_id="kubelet" text="kubelet" >}}, so that workload
|
||||
Pods can access hardware features that relate to the Node where that Pod is running.
|
||||
You can deploy a device plugin as a {{< glossary_tooltip term_id="daemonset" >}},
|
||||
or install the device plugin software directly on each target Node.
|
||||
-->
|
||||
设备插件将资源告知 {{< glossary_tooltip term_id="kubelet" text="kubelet" >}} ，以便相关节点上运行的工作负载Pod可以访问硬件功能。
|
||||
<!--
|
||||
See
|
||||
|
||||
[Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
for more information.
|
||||
-->
|
||||
更多信息请查阅[设备插件](/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 干扰（Disruption）
|
||||
id: disruption
|
||||
date: 2019-09-10
|
||||
full_link: /zh/docs/concepts/workloads/pods/disruptions/
|
||||
short_description: >
|
||||
导致 Pod 服务停止的事件。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
干扰是指导致一个或者多个 {{< glossary_tooltip term_id="pod" text="Pod" >}} 服务停止的事件。
|
||||
干扰会影响工作负载资源，比如 {{< glossary_tooltip term_id="deployment" >}} 这种依赖于受影响 Pod 的资源。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Disruption
|
||||
id: disruption
|
||||
date: 2019-09-10
|
||||
full_link: /docs/concepts/workloads/pods/disruptions/
|
||||
short_description: >
|
||||
An event that leads to Pod(s) going out of service
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
Disruptions are events that lead to one or more
|
||||
{{< glossary_tooltip term_id="pod" text="Pods" >}} going out of service.
|
||||
A disruption has consequences for workload resources, such as
|
||||
{{< glossary_tooltip term_id="deployment" >}}, that rely on the affected
|
||||
Pods.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
If you, as cluster operator, destroy a Pod that belongs to an application,
|
||||
Kubernetes terms that a _voluntary disruption_. If a Pod goes offline
|
||||
because of a Node failure, or an outage affecting a wider failure zone,
|
||||
Kubernetes terms that an _involuntary disruption_.
|
||||
|
||||
See [Disruptions](/docs/concepts/workloads/pods/disruptions/) for more information.
|
||||
-->
|
||||
如果你作为一个集群操作人员，销毁了一个从属于某个应用的 Pod, Kubernetes 视之为**自愿干扰（Voluntary Disruption）**。
|
||||
如果由于节点故障 或者影响更大区域故障的断电导致 Pod 离线，kubernetes 视之为**非愿干扰（Involuntary Disruption）**。
|
||||
|
||||
更多信息请查阅[Disruptions](/zh/docs/concepts/workloads/pods/disruptions/)
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: Docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
short_description: >
|
||||
Docker 是一种可以提供操作系统级别虚拟化（也称作容器）的软件技术。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: https://docs.docker.com/engine/
|
||||
short_description: >
|
||||
Docker is a software technology providing operating-system-level virtualization also known as containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Docker (specifically, Docker Engine) is a software technology providing operating-system-level virtualization also known as {{< glossary_tooltip text="containers" term_id="container" >}}.
|
||||
-->
|
||||
|
||||
Docker（这里特指 Docker 引擎） 是一种可以提供操作系统级别虚拟化（也称作{{< glossary_tooltip text="容器" term_id="container" >}}）的软件技术。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Docker uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines (VMs).
|
||||
-->
|
||||
|
||||
Docker 使用了 Linux 内核中的资源隔离特性（如 cgroup 和内核命名空间）以及支持联合文件系统（如 OverlayFS 和其他），
|
||||
允许多个相互独立的“容器”一起运行在同一 Linux 实例上，从而避免启动和维护虚拟机（VMs）的开销。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Dockershim
|
||||
id: dockershim
|
||||
date: 2022-04-15
|
||||
full_link: /zh/dockershim
|
||||
short_description: >
|
||||
dockershim 是 Kubernetes v1.23 及之前版本中的一个组件，Kubernetes 系统组件通过它与 Docker Engine 通信。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Dockershim
|
||||
id: dockershim
|
||||
date: 2022-04-15
|
||||
full_link: /dockershim
|
||||
short_description: >
|
||||
A component of Kubernetes v1.23 and earlier, which allows Kubernetes system components to communicate with Docker Engine.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
The dockershim is a component of Kubernetes version 1.23 and earlier. It allows the kubelet
|
||||
to communicate with {{< glossary_tooltip text="Docker Engine" term_id="docker" >}}.
|
||||
-->
|
||||
|
||||
dockershim 是 Kubernetes v1.23 及之前版本中的一个组件。
|
||||
Kubernetes 系统组件通过它与 {{< glossary_tooltip text="Docker Engine" term_id="docker" >}} 通信。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Starting with version 1.24, dockershim has been removed from Kubernetes. For more information, see [Dockershim FAQ](/dockershim).
|
||||
-->
|
||||
从 Kubernetes v1.24 开始，dockershim 已从 Kubernetes 中移除.
|
||||
想了解更多信息，可参考[移除 Dockershim 的常见问题](/zh/dockershim)。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 下游（Downstream）
|
||||
id: downstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
可以指：Kubernetes 生态系统中依赖于核心 Kubernetes 代码库或分支代码库的代码。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Downstream (disambiguation)
|
||||
id: downstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
|
||||
-->
|
||||
|
||||
可以指：Kubernetes 生态系统中依赖于核心 Kubernetes 代码库或分支代码库的代码。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* In the **Kubernetes Community**: Conversations often use *downstream* to mean the ecosystem, code, or third-party tools that rely on the core Kubernetes codebase. For example, a new feature in Kubernetes may be adopted by applications *downstream* to improve their functionality.
|
||||
* In **GitHub** or **git**: The convention is to refer to a forked repo as *downstream*, whereas the source repo is considered *upstream*.
|
||||
-->
|
||||
|
||||
* 在 **Kubernetes 社区**中：*下游(downstream)* 在人们交流中常用来表示那些依赖核心 Kubernetes 代码库的生态系统、代码或者第三方工具。例如，Kubernetes 的一个新特性可以被*下游(downstream)* 应用采用，以提升它们的功能性。
|
||||
* 在 **GitHub** 或 **git** 中：约定用*下游(downstream)* 表示分支代码库，源代码库被认为是*上游(upstream)*。
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: 动态卷供应（Dynamic Volume Provisioning）
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/dynamic-provisioning/
|
||||
short_description: >
|
||||
允许用户请求自动创建存储卷。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Dynamic Volume Provisioning
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/dynamic-provisioning
|
||||
short_description: >
|
||||
Allows users to request automatic creation of storage Volumes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Allows users to request automatic creation of storage {{< glossary_tooltip text="Volumes" term_id="volume" >}}.
|
||||
-->
|
||||
|
||||
允许用户请求自动创建存储 {{< glossary_tooltip text="卷" term_id="volume" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Dynamic provisioning eliminates the need for cluster administrators to pre-provision storage. Instead, it automatically provisions storage by user request. Dynamic volume provisioning is based on an API object, {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}}, referring to a {{< glossary_tooltip text="Volume Plugin" term_id="volume-plugin" >}} that provisions a {{< glossary_tooltip text="Volume" term_id="volume" >}} and the set of parameters to pass to the Volume Plugin.
|
||||
-->
|
||||
|
||||
动态供应让集群管理员无需再预先供应存储。相反，它通过用户请求自动地供应存储。
|
||||
动态卷供应是基于 API 对象 {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}} 的，
|
||||
StorageClass 可以引用 {{< glossary_tooltip text="卷插件" term_id="volume-plugin" >}} 提供的
|
||||
{{< glossary_tooltip text="卷" term_id="volume" >}}，也可以引用传递给卷插件（Volume Plugin）的参数集。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: EndpointSlice
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/endpoint-slices/
|
||||
short_description: >
|
||||
一种将网络端点与 Kubernetes 资源组合在一起的方法。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
一种将网络端点与 Kubernetes 资源组合在一起的方法。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: EndpointSlice
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/endpoint-slices/
|
||||
short_description: >
|
||||
A way to group network endpoints together with Kubernetes resources.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
A way to group network endpoints together with Kubernetes resources.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A scalable and extensible way to group network endpoints together. These can be
|
||||
used by {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to
|
||||
establish network routes on each {{< glossary_tooltip text="node" term_id="node" >}}.
|
||||
-->
|
||||
|
||||
|
||||
一种将网络端点组合在一起的可扩缩、可扩展方式。
|
||||
它们将被 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} 用于在
|
||||
每个 {{< glossary_tooltip text="节点" term_id="node">}} 上建立网络路由。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 端点（Endpoints）
|
||||
id: endpoints
|
||||
date: 2020-04-23
|
||||
full_link:
|
||||
short_description: >
|
||||
端点负责记录与服务（Service）的选择器相匹配的 Pods 的 IP 地址。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
端点负责记录与服务的{{< glossary_tooltip text="选择器" term_id="selector" >}}相匹配的 Pods 的 IP 地址。
|
||||
|
||||
<!--
|
||||
title: Endpoints
|
||||
id: endpoints
|
||||
date: 2020-04-23
|
||||
full_link:
|
||||
short_description: >
|
||||
Endpoints track the IP addresses of Pods with matching Service selectors.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
|
||||
Endpoints track the IP addresses of Pods with matching {{< glossary_tooltip text="selectors" term_id="selector" >}}.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Endpoints can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
|
||||
-->
|
||||
端点可以手动配置到{{< glossary_tooltip text="服务（Service）" term_id="service" >}}上，而不必指定选择器标识。
|
||||
<!--
|
||||
The {{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} resource provides a scalable and extensible alternative to Endpoints.
|
||||
-->
|
||||
{{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}}提供了一种可伸缩、可扩展的替代方案。
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: 临时容器（Ephemeral Container）
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /zh/docs/concepts/workloads/pods/ephemeral-containers/
|
||||
short_description: >
|
||||
你可以在 Pod 中临时运行的一种容器类型
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
你可以在 {{< glossary_tooltip term_id="pod" >}} 中临时运行的一种 {{< glossary_tooltip term_id="container" >}} 类型。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Ephemeral Container
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /docs/concepts/workloads/pods/ephemeral-containers/
|
||||
short_description: >
|
||||
A type of container type that you can temporarily run inside a Pod
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
A {{< glossary_tooltip term_id="container" >}} type that you can temporarily run inside a {{< glossary_tooltip term_id="pod" >}}.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics. Ephemeral containers have no resource or scheduling guarantees, and you should not use them to run any part of the workload itself.
|
||||
-->
|
||||
|
||||
如果想要调查运行中有问题的 Pod，可以向该 Pod 添加一个临时容器并进行诊断。
|
||||
临时容器没有资源或调度保证，因此不应该使用它们来运行任何部分的工作负荷本身。
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: etcd
|
||||
id: etcd
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/administer-cluster/configure-upgrade-etcd/
|
||||
short_description: >
|
||||
etcd 是兼具一致性和高可用性的键值数据库，用作保存 Kubernetes 所有集群数据的后台数据库。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: etcd
|
||||
id: etcd
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/
|
||||
short_description: >
|
||||
Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
|
||||
-->
|
||||
|
||||
`etcd` 是兼顾一致性与高可用性的键值数据库，可以作为保存 Kubernetes 所有集群数据的后台数据库。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
If your Kubernetes cluster uses etcd as its backing store, make sure you have a
|
||||
[back up](/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster) plan
|
||||
for those data.
|
||||
-->
|
||||
你的 Kubernetes 集群的 `etcd` 数据库通常需要有个[备份](/zh/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster)计划。
|
||||
<!--
|
||||
You can find in-depth information about etcd in the official [documentation](https://etcd.io/docs/).
|
||||
-->
|
||||
|
||||
如果想要更深入的了解 `etcd`，请参考 [etcd 文档](https://etcd.io/docs/)。
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: 事件（Event）
|
||||
id: event
|
||||
date: 2022-01-16
|
||||
full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
|
||||
short_description: >
|
||||
对集群中周处发生的事件的报告。通常用来表述系统中某种状态变更。
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Event
|
||||
id: event
|
||||
date: 2022-01-16
|
||||
full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
|
||||
short_description: >
|
||||
A report of an event somewhere in the cluster. It generally denotes some state change in the system.
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
Each Event is a report of an event somewhere in the {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
|
||||
It generally denotes some state change in the system.
|
||||
-->
|
||||
每个 Event 是{{< glossary_tooltip text="集群" term_id="cluster" >}}中某处发生的事件的报告。
|
||||
它通常用来表述系统中的某种状态变化。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Events have a limited retention time and triggers and messages may evolve with time.
|
||||
Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger,
|
||||
or the continued existence of events with that reason.
|
||||
-->
|
||||
事件的保留时间有限，随着时间推进，其触发方式和消息都可能发生变化。
|
||||
事件用户不应该对带有给定原因（反映下层触发源）的时间特征有任何依赖，
|
||||
也不要寄希望于对应该原因的事件会一直存在。
|
||||
|
||||
<!--
|
||||
Events should be treated as informative, best-effort, supplemental data.
|
||||
-->
|
||||
事件应该被视为一种告知性质的、尽力而为的、补充性质的数据。
|
||||
|
||||
<!--
|
||||
In Kubernetes, [auditing](/docs/tasks/debug/debug-cluster/audit/) generates a different kind of
|
||||
Event record (API group `audit.k8s.io`).
|
||||
-->
|
||||
在 Kubernetes 中，[审计](/zh/docs/tasks/debug/debug-cluster/audit/)
|
||||
机制会生成一种不同种类的 Event 记录（API 组为 `audit.k8s.io`）。
|
||||
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 驱逐
|
||||
id: eviction
|
||||
date: 2021-05-08
|
||||
full_link: /zh/docs/concepts/scheduling-eviction/
|
||||
short_description: >
|
||||
终止节点上一个或多个 Pod 的过程。
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Eviction
|
||||
id: eviction
|
||||
date: 2021-05-08
|
||||
full_link: /docs/concepts/scheduling-eviction/
|
||||
short_description: >
|
||||
Process of terminating one or more Pods on Nodes
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Eviction is the process of terminating one or more Pods on Nodes.
|
||||
-->
|
||||
驱逐即终止节点上一个或多个 Pod 的过程。
|
||||
<!--more-->
|
||||
<!--
|
||||
There are two kinds of eviction:
|
||||
* [Node-pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/)
|
||||
* [API-initiated eviction](/docs/reference/generated/kubernetes-api/v1.23/)
|
||||
-->
|
||||
驱逐的两种类型
|
||||
* [节点压力驱逐](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
|
||||
* [API 发起的驱逐](/docs/reference/generated/kubernetes-api/v1.23/)
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 扩展组件（Extensions）
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
short_description: >
|
||||
扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Extensions
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
short_description: >
|
||||
Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
-->
|
||||
<!--
|
||||
Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
|
||||
-->
|
||||
扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Many cluster administrators use a hosted or distribution instance of Kubernetes. These clusters come with extensions pre-installed. As a result, most Kubernetes users will not need to install [extensions](/docs/concepts/extend-kubernetes/extend-cluster/#extensions) and even fewer users will need to author new ones.
|
||||
-->
|
||||
|
||||
许多集群管理员会使用托管的 Kubernetes 或其某种发行包，这些集群预装了扩展。
|
||||
因此，大多数 Kubernetes 用户将不需要
|
||||
安装[扩展组件](/zh/docs/concepts/extend-kubernetes/extend-cluster/#extensions)，
|
||||
需要编写新的扩展组件的用户就更少了。
|
||||
@@ -0,0 +1,65 @@
|
||||
---
|
||||
title: Finalizer
|
||||
id: finalizer
|
||||
date: 2021-07-07
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/finalizers/
|
||||
short_description: >
|
||||
一个带有命名空间的键，告诉 Kubernetes 等到特定的条件被满足后，
|
||||
再完全删除被标记为删除的资源。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Finalizer
|
||||
id: finalizer
|
||||
date: 2021-07-07
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/finalizers/
|
||||
short_description: >
|
||||
A namespaced key that tells Kubernetes to wait until specific conditions are met
|
||||
before it fully deletes an object marked for deletion.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
Finalizers are namespaced keys that tell Kubernetes to wait until specific
|
||||
conditions are met before it fully deletes resources marked for deletion.
|
||||
Finalizers alert {{<glossary_tooltip text="controllers" term_id="controller">}}
|
||||
to clean up resources the deleted object owned.
|
||||
-->
|
||||
Finalizer 是带有命名空间的键，告诉 Kubernetes 等到特定的条件被满足后，
|
||||
再完全删除被标记为删除的资源。
|
||||
Finalizer 提醒{{<glossary_tooltip text="控制器" term_id="controller">}}清理被删除的对象拥有的资源。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
When you tell Kubernetes to delete an object that has finalizers specified for
|
||||
it, the Kubernetes API marks the object for deletion by populating `.metadata.deletionTimestamp`,
|
||||
and returns a `202` status code (HTTP "Accepted"). The target object remains in a terminating state while the
|
||||
control plane, or other components, take the actions defined by the finalizers.
|
||||
After these actions are complete, the controller removes the relevant finalizers
|
||||
from the target object. When the `metadata.finalizers` field is empty,
|
||||
Kubernetes considers the deletion complete.
|
||||
-->
|
||||
当你告诉 Kubernetes 删除一个指定了 Finalizer 的对象时，
|
||||
Kubernetes API 通过填充 `.metadata.deletionTimestamp` 来标记要删除的对象，
|
||||
并返回`202`状态码 (HTTP "已接受") 使其进入只读状态。
|
||||
此时控制平面或其他组件会采取 Finalizer 所定义的行动，
|
||||
而目标对象仍然处于终止中（Terminating）的状态。
|
||||
这些行动完成后，控制器会删除目标对象相关的 Finalizer。
|
||||
当 `metadata.finalizers` 字段为空时，Kubernetes 认为删除已完成。
|
||||
|
||||
<!--
|
||||
You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
|
||||
of resources. For example, you can define a finalizer to clean up related resources or
|
||||
infrastructure before the controller deletes the target resource.
|
||||
-->
|
||||
你可以使用 Finalizer 控制资源的{{<glossary_tooltip text="垃圾收集" term_id="garbage-collection">}}。
|
||||
例如，你可以定义一个 Finalizer，在删除目标资源前清理相关资源或基础设施。
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: FlexVolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
FlexVolume 是一个已弃用的接口，用于创建树外卷插件。
|
||||
{{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}}
|
||||
是比 Flexvolume 更新的接口，它解决了 Flexvolumes 的一些问题。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
title: FlexVolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
FlexVolume is a deprecated interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface that addresses several problems with FlexVolume.
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
-->
|
||||
<!--
|
||||
FlexVolume is a deprecated interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface that addresses several problems with FlexVolume.
|
||||
-->
|
||||
FlexVolume 是一个已弃用的接口，用于创建树外卷插件。
|
||||
{{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}}
|
||||
是比 Flexvolume 更新的接口，它解决了 Flexvolume 的一些问题。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
FlexVolumes enable users to write their own drivers and add support for their volumes in Kubernetes. FlexVolume driver binaries and dependencies must be installed on host machines. This requires root access. The Storage SIG suggests implementing a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver if possible since it addresses the limitations with FlexVolumes.
|
||||
-->
|
||||
Flexvolume 允许用户编写自己的驱动程序，并在 Kubernetes 中加入对用户自己的数据卷的支持。
|
||||
FlexVolume 驱动程序的二进制文件和依赖项必须安装在主机上。
|
||||
这需要 root 权限。如果可能的话，SIG Storage 建议实现
|
||||
{{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序，
|
||||
因为它解决了 Flexvolumes 的限制。
|
||||
|
||||
<!--
|
||||
* [FlexVolume in the Kubernetes documentation](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [More information on FlexVolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md)
|
||||
* [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
|
||||
-->
|
||||
* [Kubernetes 文档中的 Flexvolume](/zh/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [更多关于 Flexvolumes 的信息](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md)
|
||||
* [存储供应商的卷插件 FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: 垃圾收集
|
||||
id: garbage-collection
|
||||
date: 2021-07-07
|
||||
full_link: /zh/docs/concepts/workloads/controllers/garbage-collection/
|
||||
short_description: >
|
||||
Kubernetes 用于清理集群资源的各种机制的统称。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
---
|
||||
<!--
|
||||
title: Garbage Collection
|
||||
id: garbage-collection
|
||||
date: 2021-07-07
|
||||
full_link: /docs/concepts/workloads/controllers/garbage-collection/
|
||||
short_description: >
|
||||
A collective term for the various mechanisms Kubernetes uses to clean up cluster
|
||||
resources.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
-->
|
||||
|
||||
<!--
|
||||
Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up
|
||||
cluster resources.
|
||||
-->
|
||||
垃圾收集是 Kubernetes 用于清理集群资源的各种机制的统称。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images),
|
||||
[failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection),
|
||||
[objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/),
|
||||
[completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources
|
||||
that have expired or failed.
|
||||
-->
|
||||
Kubernetes 使用垃圾收集机制来清理资源，例如：
|
||||
[未使用的容器和镜像](/zh/docs/concepts/workloads/controllers/garbage-collection/#containers-images)、
|
||||
[失败的 Pod](/zh/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)、
|
||||
[目标资源拥有的对象](/zh/docs/concepts/overview/working-with-objects/owners-dependents/)、
|
||||
[已完成的 Job](/zh/docs/concepts/workloads/controllers/ttlafterfinished/)、
|
||||
过期或出错的资源。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: Helm Chart
|
||||
id: helm-chart
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
|
||||
short_description: >
|
||||
Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Helm Chart
|
||||
id: helm-chart
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
|
||||
short_description: >
|
||||
A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
|
||||
-->
|
||||
|
||||
Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Charts provide a reproducible way of creating and sharing Kubernetes applications.
|
||||
A single chart can be used to deploy something simple, like a memcached Pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
|
||||
-->
|
||||
|
||||
Chart 提供了一种可重现的用来创建和共享 Kubernetes 应用的方法。
|
||||
单个 Chart 可用来部署简单的系统（例如一个 memcached Pod），
|
||||
也可以用来部署复杂的系统（例如包含 HTTP 服务器、数据库、缓存等组件的完整 Web 应用堆栈）。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: Pod 水平自动扩缩器（Horizontal Pod Autoscaler）
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
short_description: >
|
||||
Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
aka:
|
||||
- HPA
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Horizontal Pod Autoscaler
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
short_description: >
|
||||
An API resource that automatically scales the number of pod replicas based on targeted CPU utilization or custom metric targets.
|
||||
|
||||
aka:
|
||||
- HPA
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
Horizontal Pod Autoscaler（Pod 水平自动扩缩器）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
HPA is typically used with {{< glossary_tooltip text="ReplicationControllers" term_id="replication-controller" >}}, {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or {{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}}. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
|
||||
-->
|
||||
|
||||
HPA 通常用于 {{< glossary_tooltip text="ReplicationControllers" term_id="replication-controller" >}}
|
||||
、{{< glossary_tooltip text="Deployments" term_id="deployment" >}}
|
||||
或者 {{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}} 上。
|
||||
HPA 不能用于不支持扩缩的对象，例如 {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: HostAliases
|
||||
id: HostAliases
|
||||
date: 2019-01-31
|
||||
full_link: /docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core
|
||||
short_description: >
|
||||
主机别名 (HostAliases) 是一组 IP 地址和主机名的映射，用于注入到 Pod 内的 hosts 文件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
主机别名 (HostAliases) 是一组 IP 地址和主机名的映射，用于注入到 {{< glossary_tooltip text="Pod" term_id="pod" >}} 内的 hosts 文件。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: HostAliases
|
||||
id: HostAliases
|
||||
date: 2019-01-31
|
||||
full_link: /docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core
|
||||
short_description: >
|
||||
A HostAliases is a mapping between the IP address and hostname to be injected into a Pod's hosts file.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
A HostAliases is a mapping between the IP address and hostname to be injected into a {{< glossary_tooltip text="Pod" term_id="pod" >}}'s hosts file.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
[HostAliases](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods.
|
||||
-->
|
||||
[HostAliases](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core)
|
||||
是一个包含主机名和 IP 地址的可选列表，配置后将被注入到 Pod 内的 hosts 文件中。
|
||||
该选项仅适用于没有配置 hostNetwork 的 Pod.
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 镜像（Image）
|
||||
id: image
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
镜像是保存的容器实例，它打包了应用运行所需的一组软件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Image
|
||||
id: image
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Stored instance of a container that holds a set of software needed to run an application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Stored instance of a {{< glossary_tooltip term_id="container" >}} that holds a set of software needed to run an application.
|
||||
-->
|
||||
|
||||
镜像是保存的{{< glossary_tooltip text="容器" term_id="container" >}}实例，它打包了应用运行所需的一组软件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A way of packaging software that allows it to be stored in a container registry, pulled to a local system, and run as an application. Meta data is included in the image that can indicate what executable to run, who built it, and other information.
|
||||
-->
|
||||
|
||||
镜像是软件打包的一种方式，可以将镜像存储在容器镜像仓库、拉取到本地系统并作为应用来运行。
|
||||
镜像中包含的元数据指明了运行什么可执行程序、是由谁构建的以及其他信息。
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: 词汇表
|
||||
layout: glossary
|
||||
noedit: true
|
||||
default_active_tag: fundamental
|
||||
weight: 5
|
||||
card:
|
||||
name: reference
|
||||
weight: 10
|
||||
title: 词汇表
|
||||
---
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Ingress
|
||||
id: ingress
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/ingress/
|
||||
short_description: >
|
||||
Ingress 是对集群中服务的外部访问进行管理的 API 对象，典型的访问方式是 HTTP。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Ingress
|
||||
id: ingress
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/ingress/
|
||||
short_description: >
|
||||
An API object that manages external access to the services in a cluster, typically HTTP.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that manages external access to the services in a cluster, typically HTTP.
|
||||
-->
|
||||
|
||||
Ingress 是对集群中服务的外部访问进行管理的 API 对象，典型的访问方式是 HTTP。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Ingress may provide load balancing, SSL termination and name-based virtual hosting.
|
||||
-->
|
||||
|
||||
Ingress 可以提供负载均衡、SSL 终结和基于名称的虚拟托管。
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 初始化容器（Init Container）
|
||||
id: init-container
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
应用容器运行前必须先运行完成的一个或多个初始化容器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Init Container
|
||||
id: init-container
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
One or more initialization containers that must run to completion before any app containers run.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
One or more initialization {{< glossary_tooltip text="containers" term_id="container" >}} that must run to completion before any app containers run.
|
||||
-->
|
||||
|
||||
应用{{< glossary_tooltip text="容器" term_id="container" >}}运行前必须先运行完成的一个或多个初始化容器。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Initialization (init) containers are like regular app containers, with one difference: init containers must run to completion before any app containers can start. Init containers run in series: each init container must run to completion before the next init container begins.
|
||||
-->
|
||||
|
||||
初始化（init）容器像常规应用容器一样，只有一点不同：初始化（init）容器必须在应用容器启动前运行完成。
|
||||
Init 容器的运行顺序：一个初始化（init）容器必须在下一个初始化（init）容器开始前运行完成。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/
|
||||
short_description: >
|
||||
Istio 是个开放平台（非 Kubernetes 特有），提供了一种统一的方式来集成微服务、管理流量、实施策略和汇总度量数据。
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/
|
||||
short_description: >
|
||||
An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
|
||||
-->
|
||||
|
||||
Istio 是个开放平台（非 Kubernetes 特有），提供了一种统一的方式来集成微服务、管理流量、实施策略和汇总度量数据。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Adding Istio does not require changing application code. It is a layer of infrastructure between a service and the network, which when combined with service deployments, is commonly referred to as a service mesh. Istio's control plane abstracts away the underlying cluster management platform, which may be Kubernetes, Mesosphere, etc.
|
||||
-->
|
||||
|
||||
添加 Istio 时不需要修改应用代码。它是基础设施的一层，介于服务和网络之间。
|
||||
当它和服务的 Deployment 相结合时，就构成了通常所谓的服务网格（Service Mesh）。
|
||||
Istio 的控制面抽象掉了底层的集群管理平台，这一集群管理平台可以是 Kubernetes、Mesosphere 等。
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/job/
|
||||
short_description: >
|
||||
Job 是需要运行完成的确定性的或批量的任务。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/job/
|
||||
short_description: >
|
||||
A finite or batch task that runs to completion.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A finite or batch task that runs to completion.
|
||||
-->
|
||||
|
||||
Job 是需要运行完成的确定性的或批量的任务。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Creates one or more {{< glossary_tooltip term_id="pod" >}} objects and ensures that a specified number of them successfully terminate. As Pods successfully complete, the Job tracks the successful completions.
|
||||
-->
|
||||
|
||||
Job 创建一个或多个 {{< glossary_tooltip term_id="Pod" >}} 对象，并确保指定数量的 Pod 成功终止。
|
||||
随着各 Pod 成功结束，Job 会跟踪记录成功完成的个数。
|
||||
@@ -0,0 +1,73 @@
|
||||
---
|
||||
title: Kops
|
||||
id: kops
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/kops/
|
||||
short_description: >
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kops
|
||||
id: kops
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/kops/
|
||||
short_description: >
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters.
|
||||
-->
|
||||
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
{{< note >}}
|
||||
kops has general availability support only for AWS.
|
||||
Support for using kops with GCE and VMware vSphere are in alpha.
|
||||
{{< /note >}}
|
||||
-->
|
||||
注意：官方仅支持 AWS，GCE 和 VMware vSphere 的支持还处于 alpha* 阶段。
|
||||
|
||||
|
||||
<!--
|
||||
`kops` provisions your cluster with:
|
||||
|
||||
* Fully automated installation
|
||||
* DNS-based cluster identification
|
||||
* Self-healing: everything runs in Auto-Scaling Groups
|
||||
* Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
|
||||
* High availability (HA) support
|
||||
* The ability to directly provision, or to generate Terraform manifests
|
||||
-->
|
||||
|
||||
`kops` 为你的集群提供了：
|
||||
|
||||
* 全自动化安装
|
||||
* 基于 DNS 的集群标识
|
||||
* 自愈功能：所有组件都在自动伸缩组（Auto-Scaling Groups）中运行
|
||||
* 有限的操作系统支持 (推荐使用 Debian，支持 Ubuntu 16.04，试验性支持 CentOS & RHEL)
|
||||
* 高可用 (HA) 支持
|
||||
* 直接提供或者生成 Terraform 清单文件的能力
|
||||
|
||||
<!--
|
||||
You can also build your own cluster using {{< glossary_tooltip term_id="kubeadm" >}} as a building block. `kops` builds on the kubeadm work.
|
||||
-->
|
||||
|
||||
你也可以将自己的集群作为一个构造块，使用 {{< glossary_tooltip term_id="kubeadm" >}} 构造集群。
|
||||
`kops` 是建立在 kubeadm 之上的。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: kube-apiserver
|
||||
id: kube-apiserver
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/command-line-tools-reference/kube-apiserver/
|
||||
short_description: >
|
||||
提供 Kubernetes API 服务的控制面组件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: kube-apiserver
|
||||
id: kube-apiserver
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/command-line-tools-reference/kube-apiserver/
|
||||
short_description: >
|
||||
Control plane component that serves the Kubernetes API.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
The API server is a component of the Kubernetes
|
||||
{{< glossary_tooltip text="control plane" term_id="control-plane" >}} that exposes the Kubernetes API.
|
||||
The API server is the front end for the Kubernetes control plane.
|
||||
-->
|
||||
API 服务器是 Kubernetes {{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件，
|
||||
该组件负责公开了 Kubernetes API，负责处理接受请求的工作。
|
||||
API 服务器是 Kubernetes 控制平面的前端。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The main implementation of a Kubernetes API server is [kube-apiserver](/docs/reference/generated/kube-apiserver/).
|
||||
kube-apiserver is designed to scale horizontally—that is, it scales by deploying more instances.
|
||||
You can run several instances of kube-apiserver and balance traffic between those instances.
|
||||
-->
|
||||
Kubernetes API 服务器的主要实现是 [kube-apiserver](/zh/docs/reference/command-line-tools-reference/kube-apiserver/)。
|
||||
`kube-apiserver` 设计上考虑了水平扩缩，也就是说，它可通过部署多个实例来进行扩缩。
|
||||
你可以运行 `kube-apiserver` 的多个实例，并在这些实例之间平衡流量。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: kube-controller-manager
|
||||
id: kube-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-controller-manager/
|
||||
short_description: >
|
||||
主节点上运行控制器的组件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: kube-controller-manager
|
||||
id: kube-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-controller-manager/
|
||||
short_description: >
|
||||
Component on the master that runs controllers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Control plane component that runs
|
||||
{{< glossary_tooltip text="controller" term_id="controller" >}} processes.
|
||||
-->
|
||||
[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 {{< 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" >}}都是一个单独的进程，
|
||||
但是为了降低复杂性，它们都被编译到同一个可执行文件，并在同一个进程中运行。
|
||||
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: kube-proxy
|
||||
id: kube-proxy
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/command-line-tools-reference/kube-proxy/
|
||||
short_description: >
|
||||
`kube-proxy` 是集群中每个节点上运行的网络代理。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- networking
|
||||
---
|
||||
<!-- ---
|
||||
title: kube-proxy
|
||||
id: kube-proxy
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/command-line-tools-reference/kube-proxy/
|
||||
short_description: >
|
||||
`kube-proxy` is a network proxy that runs on each node in the cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- networking
|
||||
--- -->
|
||||
<!--
|
||||
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](/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 仅做流量转发。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: kube-scheduler
|
||||
id: kube-scheduler
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/command-line-tools-reference/kube-scheduler/
|
||||
short_description: >
|
||||
控制平面组件，负责监视新创建的、未指定运行节点的 Pod，选择节点让 Pod 在上面运行。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- scheduler
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: kube-scheduler
|
||||
id: kube-scheduler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/command-line-tools-reference/kube-scheduler/
|
||||
short_description: >
|
||||
Control plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Control plane component that watches for newly created
|
||||
{{< glossary_tooltip term_id="pod" text="Pods" >}} with no assigned
|
||||
{{< glossary_tooltip term_id="node" text="node">}}, and selects a node for them
|
||||
to run on.-->
|
||||
|
||||
`kube-scheduler` 是{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件，
|
||||
负责监视新创建的、未指定运行{{< glossary_tooltip term_id="node" text="节点（node）">}}的 {{< glossary_tooltip term_id="pod" text="Pods" >}}，
|
||||
并选择节点来让 Pod 在上面运行。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
||||
-->
|
||||
|
||||
调度决策考虑的因素包括单个 Pod 及 Pods 集合的资源需求、软硬件及策略约束、
|
||||
亲和性及反亲和性规范、数据位置、工作负载间的干扰及最后时限。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: Kubeadm
|
||||
id: kubeadm
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/setup/production-environment/tools/kubeadm/
|
||||
short_description: >
|
||||
用来快速安装 Kubernetes 并搭建安全稳定的集群的工具。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Kubeadm
|
||||
id: kubeadm
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kubeadm/
|
||||
short_description: >
|
||||
A tool for quickly installing Kubernetes and setting up a secure cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
-->
|
||||
|
||||
<!--
|
||||
A tool for quickly installing Kubernetes and setting up a secure cluster.
|
||||
-->
|
||||
用来快速安装 Kubernetes 并搭建安全稳定的集群的工具。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can use kubeadm to install both the control plane and the {{< glossary_tooltip text="worker node" term_id="node" >}} components.
|
||||
-->
|
||||
你可以使用 kubeadm 安装控制面和
|
||||
{{< glossary_tooltip text="工作节点" term_id="node" >}}
|
||||
组件。
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Kubectl
|
||||
id: kubectl
|
||||
date: 2018-04-12
|
||||
full_link: /docs/user-guide/kubectl-overview/
|
||||
short_description: >
|
||||
kubectl 是用来和 Kubernetes 集群进行通信的命令行工具。
|
||||
|
||||
aka:
|
||||
- kubectl
|
||||
tags:
|
||||
- tool
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kubectl
|
||||
id: kubectl
|
||||
date: 2018-04-12
|
||||
full_link: /docs/user-guide/kubectl-overview/
|
||||
short_description: >
|
||||
A command line tool for communicating with a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
- kubectl
|
||||
tags:
|
||||
- tool
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Command line tool for communicating with a Kubernetes cluster's
|
||||
{{< glossary_tooltip text="control plane" term_id="control-plane" >}},
|
||||
using the Kubernetes API.
|
||||
-->
|
||||
|
||||
kubectl 是使用 Kubernetes API 与 Kubernetes
|
||||
集群的{{<glossary_tooltip text="控制面" term_id="control-plane" >}}进行通信的命令行工具。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can use `kubectl` to create, inspect, update, and delete Kubernetes objects.
|
||||
-->
|
||||
|
||||
你可以使用 `kubectl` 创建、检视、更新和删除 Kubernetes 对象。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Kubelet
|
||||
id: kubelet
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kubelet
|
||||
short_description: >
|
||||
一个在集群中每个节点上运行的代理。它保证容器都运行在 Pod 中。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
<!--
|
||||
title: Kubelet
|
||||
id: kubelet
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kubelet
|
||||
short_description: >
|
||||
An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
-->
|
||||
|
||||
<!--
|
||||
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" >}}.
|
||||
-->
|
||||
`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 不会管理不是由 Kubernetes 创建的容器。
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Kubernetes API
|
||||
id: kubernetes-api
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/kubernetes-api/
|
||||
short_description: >
|
||||
Kubernetes API 是通过 RESTful 接口提供 Kubernetes 功能服务并负责集群状态存储的应用程序。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kubernetes API
|
||||
id: kubernetes-api
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/kubernetes-api/
|
||||
short_description: >
|
||||
The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
|
||||
-->
|
||||
|
||||
Kubernetes API 是通过 RESTful 接口提供 Kubernetes 功能服务并负责集群状态存储的应用程序。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API. The API allows configuration to be managed in a declarative way. Users can interact with the Kubernetes API directly, or via tools like `kubectl`. The core Kubernetes API is flexible and can also be extended to support custom resources.
|
||||
-->
|
||||
|
||||
Kubernetes 资源和"意向记录"都是作为 API 对象储存的，并可以通过调用 RESTful 风格的 API 进行修改。
|
||||
API 允许以声明方式管理配置。
|
||||
用户可以直接和 Kubernetes API 交互，也可以通过 `kubectl` 这样的工具进行交互。
|
||||
核心的 Kubernetes API 是很灵活的，可以扩展以支持定制资源。
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 标签（Label）
|
||||
id: label
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/labels/
|
||||
short_description: >
|
||||
用来为对象设置可标识的属性标记；这些标记对用户而言是有意义且重要的。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Label
|
||||
id: label
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/labels/
|
||||
short_description: >
|
||||
Tags objects with identifying attributes that are meaningful and relevant to users.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
Tags objects with identifying attributes that are meaningful and relevant to users.
|
||||
-->
|
||||
|
||||
用来为对象设置可标识的属性标记；这些标记对用户而言是有意义且重要的。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Labels are key/value pairs that are attached to objects such as {{< glossary_tooltip text="Pods" term_id="pod" >}}. They are used to organize and to select subsets of objects.
|
||||
-->
|
||||
|
||||
标签是一些关联到 {{< glossary_tooltip text="Pods" term_id="pod" >}} 这类对象上的键值对。
|
||||
它们通常用来组织和选择对象子集。
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: LimitRange
|
||||
id: limitrange
|
||||
date: 2019-04-15
|
||||
full_link: /docs/concepts/policy/limit-range/
|
||||
short_description: >
|
||||
提供约束来限制命名空间中每个容器或 Pod 的资源消耗。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: LimitRange
|
||||
id: limitrange
|
||||
date: 2019-04-15
|
||||
full_link: /docs/concepts/policy/limit-range/
|
||||
short_description: >
|
||||
Provides constraints to limit resource consumption per Containers or Pods in a namespace.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Provides constraints to limit resource consumption per {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
|
||||
-->
|
||||
提供约束来限制命名空间中每个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
LimitRange limits the quantity of objects that can be created by type,
|
||||
as well as the amount of compute resources that may be requested/consumed by individual {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
|
||||
-->
|
||||
LimitRange 按照类型来限制命名空间中对象能够创建的数量，以及单个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 可以请求/使用的计算资源量。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 日志（Logging）
|
||||
id: logging
|
||||
date: 2019-04-04
|
||||
full_link: /zh/docs/concepts/cluster-administration/logging/
|
||||
short_description: >
|
||||
日志是集群或应用程序记录的事件列表。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
日志是 {{< glossary_tooltip text="集群（cluster）" term_id="cluster" >}} 或应用程序记录的事件列表。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Logging
|
||||
id: logging
|
||||
date: 2019-04-04
|
||||
full_link: /zh/docs/concepts/cluster-administration/logging/
|
||||
short_description: >
|
||||
Logs are the list of events that are logged by cluster or application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
Logs are the list of events that are logged by {{< glossary_tooltip text="cluster" term_id="cluster" >}} or application.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity.
|
||||
-->
|
||||
|
||||
应用程序和系统日志可以帮助你了解集群内部发生的情况。日志对于调试问题和监视集群活动非常有用。
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: 托管服务
|
||||
id: managed-service
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
由第三方供应商负责维护的一种软件产品。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Managed Service
|
||||
id: managed-service
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A software offering maintained by a third-party provider.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
-->
|
||||
|
||||
<!--
|
||||
A software offering maintained by a third-party provider.
|
||||
-->
|
||||
由第三方供应商负责维护的一种软件产品。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Some examples of Managed Services are AWS EC2, Azure SQL Database, and
|
||||
GCP Pub/Sub, but they can be any software offering that can be used by an application.
|
||||
[Service Catalog](/docs/concepts/extend-kubernetes/service-catalog/) provides a way to
|
||||
list, provision, and bind with Managed Services offered by
|
||||
{{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
|
||||
-->
|
||||
托管服务的一些例子有 AWS EC2、Azure SQL 数据库和 GCP Pub/Sub 等，
|
||||
不过它们也可以是可以被某应用使用的任何软件交付件。
|
||||
[服务目录](/zh/docs/concepts/extend-kubernetes/service-catalog/)
|
||||
提供了一种方法用来列举、制备和绑定到
|
||||
{{< glossary_tooltip text="服务代理商（Service Brokers）" term_id="service-broker" >}}
|
||||
所提供的托管服务。
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: 清单（Manifest）
|
||||
id: manifest
|
||||
date: 2019-06-28
|
||||
short_description: >
|
||||
一个或多个 Kubernetes API 对象的序列化规范。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
JSON 或 YAML 格式的 Kubernetes API 对象规范。
|
||||
|
||||
<!--
|
||||
title: Manifest
|
||||
id: manifest
|
||||
date: 2019-06-28
|
||||
short_description: >
|
||||
A serialized specification of one or more Kubernetes API objects.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
Specification of a Kubernetes API object in JSON or YAML format.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A manifest specifies the desired state of an object that Kubernetes will maintain when you apply the manifest. Each configuration file can contain multiple manifests.
|
||||
-->
|
||||
清单指定了在应用该清单时 kubernetes 将维护的对象的期望状态。每个配置文件可包含多个清单。
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: Master
|
||||
id: master
|
||||
date: 2020-04-16
|
||||
short_description: >
|
||||
遗留术语，作为运行控制平面的节点的同义词使用。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
遗留术语，作为运行 {{< glossary_tooltip text="控制平面" term_id="control-plane" >}} 的 {{< glossary_tooltip text="节点" term_id="node" >}} 的同义词使用。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Master
|
||||
id: master
|
||||
date: 2020-04-16
|
||||
short_description: >
|
||||
Legacy term, used as synonym for nodes running the control plane.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
Legacy term, used as synonym for {{< glossary_tooltip text="nodes" term_id="node" >}} hosting the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The term is still being used by some provisioning tools, such as {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}}, and managed services, to {{< glossary_tooltip text="label" term_id="label" >}} {{< glossary_tooltip text="nodes" term_id="node" >}} with `kubernetes.io/role` and control placement of {{< glossary_tooltip text="control plane" term_id="control-plane" >}} {{< glossary_tooltip text="pods" term_id="pod" >}}.
|
||||
-->
|
||||
该术语仍被一些配置工具使用，如 {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}} 以及托管的服务，为 {{< glossary_tooltip text="节点（nodes）" term_id="node" >}} 添加 `kubernetes.io/role` 的 {{< glossary_tooltip text="标签（label）" term_id="label" >}}，以及管理控制平面 Pod 的调度。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 成员（Member）
|
||||
id: member
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
K8s 社区中持续活跃的贡献者。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Member
|
||||
id: member
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A continuously active contributor in the K8s community.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A continuously active {{< glossary_tooltip text="contributor" term_id="contributor" >}} in the K8s community.
|
||||
-->
|
||||
|
||||
K8s 社区中持续活跃的{{< glossary_tooltip text="贡献者（contributor）" term_id="contributor" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Members can have issues and PRs assigned to them and participate in {{< glossary_tooltip text="special interest groups (SIGs)" term_id="sig" >}} through GitHub teams. Pre-submit tests are automatically run for members' PRs. A member is expected to remain an active contributor to the community.
|
||||
-->
|
||||
|
||||
可以将问题单（issue）和 PR 指派给成员（Member），成员（Member）也可以通过 GitHub 小组加入 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}}。针对成员（Member）所提交的 PR，系统自动运行提交前测试。成员（Member）应该是持续活跃的社区贡献者。
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Minikube
|
||||
id: minikube
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/minikube/
|
||||
short_description: >
|
||||
Minikube 是用来在本地运行 Kubernetes 的一种工具。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Minikube
|
||||
id: minikube
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/minikube/
|
||||
short_description: >
|
||||
A tool for running Kubernetes locally.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A tool for running Kubernetes locally.
|
||||
-->
|
||||
|
||||
Minikube 是用来在本地运行 Kubernetes 的一种工具。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Minikube runs a single-node cluster inside a VM on your computer.
|
||||
You can use Minikube to
|
||||
[try Kubernetes in a learning environment](/docs/setup/learning-environment/).
|
||||
-->
|
||||
|
||||
Minikube 在用户计算机上的一个虚拟机内运行单节点 Kubernetes 集群。
|
||||
你可以使用 Minikube
|
||||
[在学习环境中尝试 Kubernetes](/zh/docs/setup/learning-environment/).
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 镜像 Pod（Mirror Pod）
|
||||
id: 静态-pod
|
||||
date: 2019-08-06
|
||||
short_description: >
|
||||
API 服务器中的一个对象，用于跟踪 kubelet 上的静态 pod。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- 基本的
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Mirror Pod
|
||||
id: mirror-pod
|
||||
date: 2019-08-06
|
||||
short_description: >
|
||||
An object in the API server that tracks a static pod on a kubelet.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A {{< glossary_tooltip text="pod" term_id="pod" >}} object that a kubelet uses
|
||||
to represent a {{< glossary_tooltip text="static pod" term_id="static-pod" >}}
|
||||
-->
|
||||
镜像 Pod（Mirror Pod）是被 kubelet 用来代表{{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}} 的
|
||||
{{< glossary_tooltip text="pod" term_id="pod" >}} 对象。
|
||||
|
||||
<!--more-->
|
||||
<!--更多-->
|
||||
|
||||
<!--
|
||||
When the kubelet finds a static pod in its configuration, it automatically tries to
|
||||
create a Pod object on the Kubernetes API server for it. This means that the pod
|
||||
will be visible on the API server, but cannot be controlled from there.
|
||||
|
||||
(For example, removing a mirror pod will not stop the kubelet daemon from running it).
|
||||
-->
|
||||
当 kubelet 在其配置中发现一个静态容器时，
|
||||
它会自动地尝试在 Kubernetes API 服务器上为它创建 Pod 对象。
|
||||
这意味着 pod 在 API 服务器上将是可见的，但不能在其上进行控制。
|
||||
|
||||
（例如，删除镜像 Pod 也不会阻止 kubelet 守护进程继续运行它）。
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 名称（Name）
|
||||
id: name
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/names/
|
||||
short_description: >
|
||||
客户端提供的字符串，用来指代资源 URL 中的对象，如 `/api/v1/pods/some-name`。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Name
|
||||
id: name
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/names/
|
||||
short_description: >
|
||||
A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
|
||||
-->
|
||||
|
||||
客户端提供的字符串，引用资源 url 中的对象，如`/api/v1/pods/some name`。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Only one object of a given kind can have a given name at a time. However, if you delete the object, you can make a new object with the same name.
|
||||
-->
|
||||
|
||||
某一时刻，只能有一个给定类型的对象具有给定的名称。但是，如果删除该对象，则可以创建同名的新对象。
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: 名字空间（Namespace）
|
||||
id: namespace
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/namespaces/
|
||||
short_description: >
|
||||
名字空间是 Kubernetes 用来支持隔离单个集群中的资源组的一种抽象。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Namespace
|
||||
id: namespace
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/namespaces/
|
||||
short_description: >
|
||||
An abstraction used by Kubernetes to support isolation of groups of resources within a single cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An abstraction used by Kubernetes to support isolation of groups of resources within a single {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
|
||||
-->
|
||||
|
||||
名字空间是 Kubernetes 用来支持隔离单个 {{< glossary_tooltip text="集群" term_id="cluster" >}}中的资源组的一种抽象。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced objects _(e.g. Deployments, Services, etc)_ and not for cluster-wide objects _(e.g. StorageClass, Nodes, PersistentVolumes, etc)_.
|
||||
-->
|
||||
|
||||
名字空间用来组织集群中对象，并为集群资源划分提供了一种方法。
|
||||
同一名字空间内的资源名称必须唯一，但跨名字空间时不作要求。
|
||||
基于名字空间的作用域限定仅适用于名字空间作用域的对象（例如 Deployment、Services 等），
|
||||
而不适用于集群作用域的对象（例如 StorageClass、Node、PersistentVolume 等）。
|
||||
在一些文档里名字空间也称为命名空间。
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 网络策略
|
||||
id: network-policy
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/network-policies/
|
||||
short_description: >
|
||||
网络策略是一种规范，规定了允许 Pod 组之间、Pod 与其他网络端点之间以怎样的方式进行通信。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Network Policy
|
||||
id: network-policy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/network-policies/
|
||||
short_description: >
|
||||
A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
|
||||
-->
|
||||
|
||||
网络策略是一种规范，规定了允许 Pod 组之间、Pod 与其他网络端点之间以怎样的方式进行通信。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Network Policies help you declaratively configure which Pods are allowed to connect to each other, which namespaces are allowed to communicate, and more specifically which port numbers to enforce each policy on. `NetworkPolicy` resources use labels to select Pods and define rules which specify what traffic is allowed to the selected Pods. Network Policies are implemented by a supported network plugin provided by a network provider. Be aware that creating a network resource without a controller to implement it will have no effect.
|
||||
-->
|
||||
|
||||
网络策略帮助你声明式地配置允许哪些 Pod 之间、哪些命名空间之间允许进行通信，
|
||||
并具体配置了哪些端口号来执行各个策略。`NetworkPolicy` 资源使用标签来选择 Pod，
|
||||
并定义了所选 Pod 可以接受什么样的流量。网络策略由网络提供商提供的并被 Kubernetes 支持的网络插件实现。
|
||||
请注意，当没有控制器实现网络资源时，创建网络资源将不会生效。
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 节点压力驱逐
|
||||
id: node-pressure-eviction
|
||||
date: 2021-05-13
|
||||
full_link: /zh/docs/concepts/scheduling-eviction/node-pressure-eviction/
|
||||
short_description: >
|
||||
节点压力驱逐是 kubelet 主动使 Pod 失败以回收节点上的资源的过程。
|
||||
aka:
|
||||
- kubelet eviction
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Node-pressure eviction
|
||||
id: node-pressure-eviction
|
||||
date: 2021-05-13
|
||||
full_link: /docs/concepts/scheduling-eviction/node-pressure-eviction/
|
||||
short_description: >
|
||||
Node-pressure eviction is the process by which the kubelet proactively fails
|
||||
pods to reclaim resources on nodes.
|
||||
aka:
|
||||
- kubelet eviction
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Node-pressure eviction is the process by which the {{<glossary_tooltip term_id="kubelet" text="kubelet">}} proactively terminates
|
||||
pods to reclaim resources on nodes.
|
||||
-->
|
||||
节点压力驱逐是 {{<glossary_tooltip term_id="kubelet" text="kubelet">}} 主动终止 Pod 以回收节点上资源的过程。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The kubelet monitors resources like CPU, memory, disk space, and filesystem
|
||||
inodes on your cluster's nodes. When one or more of these resources reach
|
||||
specific consumption levels, the kubelet can proactively fail one or more pods
|
||||
on the node to reclaim resources and prevent starvation.
|
||||
-->
|
||||
kubelet 监控集群节点上的 CPU、内存、磁盘空间和文件系统 inode 等资源。
|
||||
当这些资源中的一个或多个达到特定消耗水平时，
|
||||
kubelet 可以主动使节点上的一个或多个 Pod 失效，以回收资源并防止饥饿。
|
||||
|
||||
<!--
|
||||
Node-pressure eviction is not the same as [API-initiated eviction](/docs/reference/generated/kubernetes-api/v1.23/).
|
||||
-->
|
||||
节点压力驱逐不用于 [API 发起的驱逐](/docs/reference/generated/kubernetes-api/v1.23/)。
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 节点（Node）
|
||||
id: node
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/nodes/
|
||||
short_description: >
|
||||
Kubernetes 中的工作机器称作节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Node
|
||||
id: node
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/nodes/
|
||||
short_description: >
|
||||
A node is a worker machine in Kubernetes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
A node is a worker machine in Kubernetes.
|
||||
-->
|
||||
Kubernetes 中的工作机器称作节点。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A worker node may be a VM or physical machine, depending on the cluster. It has local daemons or services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} and is managed by the control plane. The daemons on a node include {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}, and a container runtime implementing the {{< glossary_tooltip text="CRI" term_id="cri" >}} such as {{< glossary_tooltip term_id="docker" >}}.
|
||||
|
||||
In early Kubernetes versions, Nodes were called "Minions".
|
||||
-->
|
||||
工作机器可以是虚拟机也可以是物理机，取决于集群的配置。
|
||||
其上部署了运行 {{< glossary_tooltip text="Pods" term_id="pod" >}}
|
||||
所必需的本地守护进程或服务，
|
||||
并由主控组件来管理。
|
||||
节点上的的守护进程包括 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}、
|
||||
{{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}
|
||||
以及一个 {{< glossary_tooltip term_id="docker" >}} 这种
|
||||
实现了 {{< glossary_tooltip text="CRI" term_id="cri" >}}
|
||||
的容器运行时。
|
||||
|
||||
在早期的 Kubernetes 版本中，节点也称作 "Minions"。
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 对象（Object）
|
||||
id: object
|
||||
date: 2020-10-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects
|
||||
short_description: >
|
||||
Kubernetes 系统中的实体, 代表了集群的部分状态。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Object
|
||||
id: object
|
||||
date: 2020-10-12
|
||||
full_link: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects
|
||||
short_description: >
|
||||
A entity in the Kubernetes system, representing part of the state of your cluster.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
An entity in the Kubernetes system. The Kubernetes API uses these entities to represent the state
|
||||
of your cluster.
|
||||
-->
|
||||
Kubernetes 系统中的实体。Kubernetes API 用这些实体表示集群的状态。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
A Kubernetes object is typically a “record of intent”—once you create the object, the Kubernetes
|
||||
{{< glossary_tooltip text="control plane" term_id="control-plane" >}} works constantly to ensure
|
||||
that the item it represents actually exists.
|
||||
By creating an object, you're effectively telling the Kubernetes system what you want that part of
|
||||
your cluster's workload to look like; this is your cluster's desired state.
|
||||
-->
|
||||
Kubernetes 对象通常是一个“目标记录”-一旦你创建了一个对象，Kubernetes
|
||||
{{< glossary_tooltip text="控制平面（Control Plane）" term_id="control-plane" >}}
|
||||
不断工作，以确保它代表的项目确实存在。
|
||||
创建一个对象相当于告知 Kubernetes 系统：你期望这部分集群负载看起来像什么；这也就是你集群的期望状态。
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: Operator 模式
|
||||
id: operator-pattern
|
||||
date: 2019-05-21
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/operator/
|
||||
short_description: >
|
||||
一种用于管理自定义资源的专用控制器
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Operator pattern
|
||||
id: operator-pattern
|
||||
date: 2019-05-21
|
||||
full_link: /docs/concepts/extend-kubernetes/operator/
|
||||
short_description: >
|
||||
A specialized controller used to manage a custom resource
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
-->
|
||||
<!--
|
||||
The [operator pattern](/docs/concepts/extend-kubernetes/operator/) is a system
|
||||
design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom
|
||||
resources.
|
||||
-->
|
||||
[operator 模式](/zh/docs/concepts/extend-kubernetes/operator/) 是一种系统设计,
|
||||
将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can extend Kubernetes by adding controllers to your cluster, beyond the built-in
|
||||
controllers that come as part of Kubernetes itself.
|
||||
|
||||
If a running application acts as a controller and has API access to carry out tasks
|
||||
against a custom resource that's defined in the control plane, that's an example of
|
||||
the Operator pattern.
|
||||
-->
|
||||
除了使用作为 Kubernetes 自身一部分的内置控制器之外，你还可以通过
|
||||
将控制器添加到集群中来扩展 Kubernetes。
|
||||
|
||||
如果正在运行的应用程序能够充当控制器并通过 API 访问的方式来执行任务操控
|
||||
那些在控制平面中定义的自定义资源，这就是一个 operator 模式的示例。
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 持久卷申领（Persistent Volume Claim）
|
||||
id: persistent-volume-claim
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
声明在持久卷中定义的存储资源，以便可以将其挂载为容器中的卷。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Persistent Volume Claim
|
||||
id: persistent-volume-claim
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
-->
|
||||
|
||||
<!--
|
||||
Claims storage resources defined in a {{< glossary_tooltip text="PersistentVolume" term_id="persistent-volume" >}} so that it can be mounted as a volume in a {{< glossary_tooltip text="container" term_id="container" >}}.
|
||||
-->
|
||||
申领{{< glossary_tooltip text="持久卷（PersistentVolume）" term_id="persistent-volume" >}}中定义的存储资源，以便可以将其挂载为{{< glossary_tooltip text="容器（container）" term_id="container" >}}中的卷。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are described in the PersistentVolume object.
|
||||
-->
|
||||
指定存储的数量，如何访问存储（只读、读写或独占）以及如何回收存储（保留、回收或删除）。存储本身的详细信息在 PersistentVolume 对象中。
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: 持久卷（Persistent Volume）
|
||||
id: persistent-volume
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Persistent Volume
|
||||
id: persistent-volume
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual {{< glossary_tooltip text="Pod" term_id="pod" >}}.
|
||||
-->
|
||||
|
||||
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 {{< glossary_tooltip text="Pod" term_id="pod" >}} 生命周期约束的持久化资源。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
PersistentVolumes (PVs) provide an API that abstracts details of how storage is provided from how it is consumed.
|
||||
PVs are used directly in scenarios where storage can be created ahead of time (static provisioning).
|
||||
For scenarios that require on-demand storage (dynamic provisioning), PersistentVolumeClaims (PVCs) are used instead.
|
||||
-->
|
||||
|
||||
持久卷（PersistentVolumes，PV）提供了一个 API，该 API 对存储的供应方式细节进行抽象，令其与使用方式相分离。
|
||||
在提前创建存储（静态供应）的场景中，PV 可以直接使用。
|
||||
在按需提供存储（动态供应）的场景中，需要使用 PersistentVolumeClaims (PVCs)。
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: 平台开发人员（Platform Developer）
|
||||
id: platform-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
定制 Kubernetes 平台以满足自己的项目需求的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Platform Developer
|
||||
id: platform-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who customizes the Kubernetes platform to fit the needs of their project.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who customizes the Kubernetes platform to fit the needs of their project.
|
||||
-->
|
||||
|
||||
定制 Kubernetes 平台以满足自己的项目需求的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A platform developer may, for example, use [Custom Resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) or
|
||||
[Extend the Kubernetes API with the aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
|
||||
to add functionality to their instance of Kubernetes, specifically for their application.
|
||||
Some Platform Developers are also {{< glossary_tooltip text="contributors" term_id="contributor" >}} and
|
||||
develop extensions which are contributed to the Kubernetes community.
|
||||
Others develop closed-source commercial or site-specific extensions.
|
||||
-->
|
||||
|
||||
平台开发人员可以使用[定制资源](/zh/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
||||
或[使用汇聚层扩展 Kubernetes API](/zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
|
||||
来为其 Kubernetes 实例增加功能，特别是为其应用程序添加功能。
|
||||
一些平台开发人员也是 kubernetes {{< glossary_tooltip text="贡献者" term_id="contributor" >}}，
|
||||
他们会开发贡献给 Kubernetes 社区的扩展。
|
||||
另一些平台开发人员则开发封闭源代码的商业扩展或用于特定网站的扩展。
|
||||
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
id: pod-disruption-budget
|
||||
title: Pod Disruption Budget
|
||||
full-link: /zh/docs/concepts/workloads/pods/disruptions/
|
||||
date: 2019-02-12
|
||||
short_description: >
|
||||
Pod Disruption Budget 是这样一种对象：它保证在主动中断（ voluntary disruptions）时，多实例应用的 {{< glossary_tooltip text="Pod" term_id="pod" >}} 不会少于一定的数量。
|
||||
|
||||
aka:
|
||||
- PDB
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
id: pod-disruption-budget
|
||||
title: Pod Disruption Budget
|
||||
full-link: /docs/concepts/workloads/pods/disruptions/
|
||||
date: 2019-02-12
|
||||
short_description: >
|
||||
An object that limits the number of {{< glossary_tooltip text="Pods" term_id="pod" >}} of a replicated application, that are down simultaneously from voluntary disruptions.
|
||||
|
||||
aka:
|
||||
- PDB
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A [Pod Disruption Budget](/docs/concepts/workloads/pods/disruptions/) allows an
|
||||
application owner to create an object for a replicated application, that ensures
|
||||
a certain number or percentage of Pods with an assigned label will not be voluntarily
|
||||
evicted at any point in time.
|
||||
|
||||
Involuntary disruptions cannot be prevented by PDBs; however they
|
||||
do count against the budget.
|
||||
-->
|
||||
[Pod 干扰预算（Pod Disruption Budget，PDB）](/zh/docs/concepts/workloads/pods/disruptions/)
|
||||
使应用所有者能够为多实例应用创建一个对象，来确保一定数量的具有指定标签的 Pod 在任何时候都不会被主动驱逐。
|
||||
<!--more-->
|
||||
PDB 无法防止非主动的中断，但是会计入预算（budget）。
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user