update glossary
This commit is contained in:
jialaijun
parent
10c09ed849
commit
ad8b32ffce
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Add-ons（附加组件）
|
||||
id: addons
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,5 +1,18 @@
|
|||
<!--
|
||||
---
|
||||
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
|
||||
|
|
@ -13,21 +26,8 @@ tags:
|
|||
- extension
|
||||
- security
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
<!--
|
||||
A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Aggregation Layer（聚合层）
|
||||
id: aggregation-layer
|
||||
|
|
@ -31,6 +12,24 @@ tags:
|
|||
- 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
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Annotation（注解）
|
||||
id: annotation
|
||||
|
|
@ -28,6 +11,23 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: API Group
|
||||
id: api-group
|
||||
date: 2019-09-02
|
||||
full_link: /docs/concepts/overview/kubernetes-api/#api-groups
|
||||
short_description: >
|
||||
A set of related paths in the Kubernetes API.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: API Group
|
||||
id: api-group
|
||||
|
|
@ -30,6 +12,22 @@ tags:
|
|||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: API Group
|
||||
id: api-group
|
||||
date: 2019-09-02
|
||||
full_link: /docs/concepts/overview/kubernetes-api/#api-groups
|
||||
short_description: >
|
||||
A set of related paths in the Kubernetes API.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A set of related paths in Kubernetes API.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: App Container（应用程序容器）
|
||||
id: app-container
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Application Architect（应用架构师）
|
||||
id: application-architect
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Application Developer（应用开发者）
|
||||
id: application-developer
|
||||
|
|
@ -28,6 +11,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,19 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Applications
|
||||
id: applications
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The layer where various containerized applications run.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Applications（应用）
|
||||
id: applications
|
||||
|
|
@ -25,6 +9,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Approver（批准者）
|
||||
id: approver
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Certificate（证书）
|
||||
id: certificate
|
||||
|
|
@ -28,6 +11,21 @@ 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.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: cgroup (控制组)
|
||||
id: cgroup
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: CIDR
|
||||
id: cidr
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: CLA (贡献者许可协议)
|
||||
id: cla
|
||||
|
|
@ -27,6 +10,22 @@ 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.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -14,7 +14,6 @@ tags:
|
|||
---
|
||||
|
||||
<!--
|
||||
|
||||
---
|
||||
title: Cloud Controller Manager
|
||||
id: cloud-controller-manager
|
||||
|
|
@ -29,7 +28,6 @@ tags:
|
|||
- architecture
|
||||
- operation
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,8 +10,8 @@ aka:
|
|||
tags:
|
||||
- community
|
||||
---
|
||||
<!--
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Provider
|
||||
id: cloud-provider
|
||||
|
|
@ -24,7 +24,6 @@ aka:
|
|||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 集群基础设施
|
||||
title: Cluster Infrastructure（集群基础设施）
|
||||
id: cluster-infrastructure
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
|
|
@ -22,7 +22,7 @@ short_description: >
|
|||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: 集群操作
|
||||
title: Cluster Operations（集群操作）
|
||||
id: cluster-operations
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
诸如升级集群、实现安全、存储、Ingress、网络、日志和监控之类的活动，以及管理 Kubernetes 集群所涉及的其他操作。
|
||||
管理 Kubernetes 集群所涉及的相关工作。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -18,15 +18,25 @@ id: cluster-operations
|
|||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Activities such as upgrading the clusters, implementing security, storage, ingress, networking, logging and monitoring, and other operations involved in managing a Kubernetes cluster.
|
||||
The work involved in managing a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Activities such as upgrading the clusters, implementing security, storage, ingress, networking, logging and monitoring, and other operations involved in managing a Kubernetes cluster.
|
||||
The work involved in managing a Kubernetes cluster: managing
|
||||
day-to-day operations, and co-ordinating upgrades.
|
||||
-->
|
||||
诸如升级集群、实现安全、存储、Ingress、网络、日志和监控之类的活动，以及管理 Kubernetes 集群所涉及的其他操作。
|
||||
Kubernates管理相关工作包括：日常管理操作和协调升级。
|
||||
|
||||
<!--
|
||||
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.
|
||||
-->
|
||||
群集操作工作的示例包括:部署新节点来扩容集群；执行软件升级；实施安全控制；添加或删除存储；配置集群网络；
|
||||
管理集群范围的可观测性；响应集群事件。
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 集群操作者
|
||||
title: Cluster Operator（集群操作者）
|
||||
id: cluster-operator
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
|
|
@ -35,6 +35,7 @@ tags:
|
|||
<!--
|
||||
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://coreos.com/operators) that extends the Kubernetes API.
|
||||
-->
|
||||
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Cluster（集群）
|
||||
id: cluster
|
||||
|
|
@ -29,6 +11,23 @@ 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.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 云原生计算基金会 (CNCF)
|
||||
title: CNCF（云原生计算基金会）
|
||||
id: cncf
|
||||
date: 2019-05-26
|
||||
full_link: https://cncf.io/
|
||||
|
|
|
|||
|
|
@ -14,10 +14,10 @@ tags:
|
|||
|
||||
<!--
|
||||
---
|
||||
title: CNI (Container network interface)
|
||||
title: Container network interface (CNI)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 代码贡献者
|
||||
title: Code Contributor（代码贡献者）
|
||||
id: code-contributor
|
||||
date: 2018-04-12
|
||||
full_link: /docs/community/devel/
|
||||
|
|
|
|||
|
|
@ -16,9 +16,9 @@ tags:
|
|||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
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 config files in a volume.
|
||||
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:
|
||||
|
|
@ -27,15 +27,18 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {{< glossary_tooltip text="volume" term_id="volume" >}}.
|
||||
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 对象，用来将非机密性的数据保存到健值对中。使用时可以用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
ConfigMap 是一种 API 对象，用来将非机密性的数据保存到健值对中。使用时,{{< glossary_tooltip text="Pods" term_id="pod" >}} 可以将其用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/).
|
||||
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="container" >}} 解耦，便于应用配置的修改。当您需要储存机密信息时可以使用 [Secret](/docs/concepts/configuration/secret/) 对象。
|
||||
ConfigMap 将您的环境配置信息和 {{< glossary_tooltip text="容器镜像" term_id="image" >}} 解耦，便于应用配置的修改。
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: 容器环境变量
|
||||
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:
|
||||
|
|
@ -16,7 +16,7 @@ tags:
|
|||
title: Container Environment Variables
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/containers/container-environment/
|
||||
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.
|
||||
|
||||
|
|
@ -27,14 +27,14 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
|
||||
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.
|
||||
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）这样的集群资源信息。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 容器生命周期钩子
|
||||
title: Container Lifecycle Hooks（容器生命周期钩子）
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/containers/container-lifecycle-hooks/
|
||||
|
|
@ -15,11 +15,11 @@ tags:
|
|||
title: Container Lifecycle Hooks
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/containers/container-lifecycle-hooks/
|
||||
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:
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: 容器运行环境（Container Runtime）
|
||||
title: Container Runtime（容器运行时）
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /docs/setup/production-environment/container-runtimes
|
||||
full_link: /zh/docs/setup/production-environment/container-runtimes
|
||||
short_description: >
|
||||
容器运行环境是负责运行容器的软件。
|
||||
容器运行时是负责运行容器的软件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -28,7 +28,7 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
-->
|
||||
容器运行环境是负责运行容器的软件。
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 容器
|
||||
title: Container（容器）
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Container
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
full_link: /docs/concepts/containers/
|
||||
short_description: >
|
||||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ tags:
|
|||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
-->
|
||||
|
||||
容器是可移植、可执行的轻量级的镜像，镜像中包含软件及其相关依赖。
|
||||
容器是可移植、可执行的轻量级的镜像，包含其中的软件及其相关依赖。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,15 @@
|
|||
---
|
||||
title: 控制平面
|
||||
title: Control Plane（控制平面）
|
||||
id: control-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
Control Plane（控制平面）是指容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
|
|
@ -23,10 +23,33 @@ short_description: >
|
|||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
|
||||
-->
|
||||
容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
Control Plane（控制平面）是指容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
|
||||
<!--
|
||||
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 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" >}}
|
||||
|
||||
这些组件可以以传统的系统服务运行也可以以容器的形式运行.运行这些组件的主机过去称为master节点。
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: 控制器
|
||||
title: Controller（控制器）
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kube-controller-manager/
|
||||
full_link: /zh/docs/concepts/architecture/controller/
|
||||
short_description: >
|
||||
控制器通过 apiserver 监控集群的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Controller
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kube-controller-manager/
|
||||
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.
|
||||
|
||||
|
|
@ -27,14 +27,36 @@ tags:
|
|||
- 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.
|
||||
-->
|
||||
|
||||
|
||||
|
||||
控制器通过 {{< glossary_tooltip text="apiserver" term_id="kube-apiserver" >}} 监控集群的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
在Kubernates中，控制器通过监控 {{< glossary_tooltip text="集群" term_id="kube-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" >}}监控你的集群中的公共状态。
|
||||
|
||||
<!--
|
||||
Examples of controllers that ship with Kubernetes today are the replication controller, endpoints controller, namespace controller, and serviceaccounts controller.
|
||||
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 当前提供的部分控制器例子包括：副本控制器（replication controller）、端点控制器（endpoints controller）、命名空间控制器（namespace controller）、服务账号控制器（serviceaccounts controller）。
|
||||
其中一些控制器是运行在控制平面内部的，对Kubernates来说，他们提供核心控制操作。比如：部署控制器（deployment controller）、守护控制器（daemonset controller）、命名空间控制器（namespace controller）、持久化数据卷控制器（persistent volume
|
||||
controller）（等）都是运行在{{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}}中的。
|
||||
|
||||
|
|
|
|||
|
|
@ -2,20 +2,21 @@
|
|||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/docs/
|
||||
full_link: https://cri-o.io/#what-is-cri-o
|
||||
short_description: >
|
||||
专用于 Kubernetes 的轻量级容器运行环境
|
||||
专用于 Kubernetes 的轻量级容器运行时软件
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
<!--
|
||||
---
|
||||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/docs/
|
||||
full_link: https://cri-o.io/#what-is-cri-o
|
||||
short_description: >
|
||||
A lightweight container runtime specifically for Kubernetes
|
||||
|
||||
|
|
@ -23,18 +24,24 @@ aka:
|
|||
tags:
|
||||
- tool
|
||||
--- -->
|
||||
<!-- A tool that lets you use OCI container runtimes with Kubernetes CRI. -->
|
||||
<!--
|
||||
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" >}}
|
||||
<!--
|
||||
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](http://www.github.com/opencontainers/runtime-spec). -->
|
||||
CRI-O 是 {{< glossary_tooltip term_id="cri" >}} 的实现，可启用与开放容器倡议 Open Container Initiative（OCI）兼容的 {{< glossary_tooltip text="container" term_id="container" >}} 运行环境[运行时规范](http://www.github.com/opencontainers/runtime-spec)。
|
||||
[runtime spec](https://www.github.com/opencontainers/runtime-spec).
|
||||
-->
|
||||
CRI-O 是 {{< glossary_tooltip text="cri" term_id="cri" >}} 的实现，与开放容器倡议 Open Container Initiative（OCI）兼容的 {{< glossary_tooltip text="container" term_id="container" >}} [运行时规范](https://www.github.com/opencontainers/runtime-spec)。
|
||||
|
||||
<!-- Deploying CRI-O allows Kubernetes to use any OCI-compliant runtime as the 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 容器镜像。
|
||||
OCI container images from remote registries.
|
||||
-->
|
||||
部署 CRI-O 允许 Kubernetes 使用任何符合 OCI 的运行时，作为容器运行环境去运行 {{< glossary_tooltip text="Pods" term_id="pod" >}}，并从远程注册表获取 OCI 容器镜像。
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 容器运行时接口 (CRI)
|
||||
title: CRI（容器运行时接口）
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /zh/docs/concepts/overview/components/#container-runtime
|
||||
|
|
@ -18,7 +18,7 @@ tags:
|
|||
title: Container runtime interface (CRI)
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /zh/docs/concepts/overview/components/#container-runtime
|
||||
full_link: /docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
An API for container runtimes to integrate with kubelet
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: CronJob
|
||||
title: CronJob（周期调度任务）
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
管理定期运行的 [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)。
|
||||
周期调度的任务（作业）。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -17,9 +17,9 @@ tags:
|
|||
title: CronJob
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/cron-jobs/
|
||||
full_link: /docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
|
||||
A repeating task (a Job) that runs on a regular schedule.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -29,10 +29,10 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/job/) that runs on a periodic schedule.
|
||||
-->
|
||||
|
||||
管理定期运行的 [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)。
|
||||
管理定期运行的 [任务](/zh/docs/concepts/workloads/controllers/job/)。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 容器存储接口 (CSI)
|
||||
title: Container Storage Interface(CSI)（容器存储接口）
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#csi
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Container Storage Interface (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#csi
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
|
||||
|
|
@ -36,13 +36,13 @@ tags:
|
|||
<!--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/Setup.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver.
|
||||
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)
|
||||
* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html)
|
||||
-->
|
||||
|
||||
CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件，而无需将这些插件的代码添加到 Kubernetes 代码仓库（外部插件）。要使用某个存储提供商的 CSI 驱动，你首先要[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/Setup.html)。然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件，而无需将这些插件的代码添加到 Kubernetes 代码仓库（外部插件）。要使用某个存储提供商的 CSI 驱动，你首先要[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/deploying.html)。然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/Drivers.html)
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/zh/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/drivers.html)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
|
||||
full_link: /zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
||||
short_description: >
|
||||
通过定制化的代码给您的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
|
||||
|
||||
|
|
@ -18,8 +18,7 @@ tags:
|
|||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
|
||||
short_description: >
|
||||
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:
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ tags:
|
|||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/daemonset/
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 数据平面
|
||||
title: Data Plane（数据平面）
|
||||
id: data-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
|
|
|
|||
|
|
@ -18,9 +18,9 @@ tags:
|
|||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/deployment/
|
||||
full_link: /docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
An API object that manages a replicated application.
|
||||
Manages a replicated application on your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -31,15 +31,17 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
An API object that manages a replicated application.
|
||||
An API object that manages a replicated application, typically by running Pods with no local state.
|
||||
-->
|
||||
|
||||
Deployment 是管理应用副本的 API 对象。
|
||||
Deployment 是管理应用副本的 API 对象，通常通过运行没有本地状态的Pods来实现。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Each replica is represented by a {{< glossary_tooltip term_id="pod" >}}, and the Pods are distributed among the nodes of a cluster.
|
||||
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 term_id="pod" >}}，并且这些 Pod 会分散运行在集群的节点上。
|
||||
应用的每个副本就是一个 {{< glossary_tooltip text="Pod" term_id="pod" >}}，并且这些 Pod 会分散运行在集群的{{< glossary_tooltip text="节点" term_id="node" >}}上。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 开发者 (释疑)
|
||||
title: Developer（开发者）
|
||||
id: developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
|
|
|
|||
|
|
@ -1,32 +1,52 @@
|
|||
---
|
||||
title: 驱动插件
|
||||
title: Device Plugin（设备插件）
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
在 Kubernetes 中运行的容器提供对供应商特定资源的访问权限。
|
||||
一种软件扩展，可以使Pod访问由特定厂商初始化或者安装的设备。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
<!--
|
||||
---
|
||||
title: Device Plugin
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
Containers running in Kubernetes that provide access to a vendor specific resource.
|
||||
Software extensions to let Pods access devices that need vendor-specific initialization or setup
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
--- -->
|
||||
<!-- Device Plugins are containers running in Kubernetes that provide access to a vendor specific resource. -->
|
||||
设备插件是在 Kubernetes 中运行的容器，可用于访问供应商特定资源。
|
||||
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
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](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) are containers running in Kubernetes that provide access to a vendor-specific resource. Device Plugins advertise these resources to {{< glossary_tooltip term_id="kubelet" >}}. They can be deployed manually or as a {{< glossary_tooltip term_id="daemonset" >}}, rather than writing custom Kubernetes code. -->
|
||||
[驱动插件](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) 是运行在 Kubernetes 中的容器，它提供对供应商特定资源的访问。驱动插件将这些资源发布到 {{< glossary_tooltip term_id="kubelet" >}}。并且可以手动部署或做为 {{< glossary_tooltip term_id="daemonset" >}}，而不用编写定制的 Kubernetes 代码。
|
||||
<!--
|
||||
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.
|
||||
-->
|
||||
更多信息请查阅[设备插件](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 干扰
|
||||
title: Disruption（干扰）
|
||||
id: disruption
|
||||
date: 2019-09-10
|
||||
full_link: /zh/docs/concepts/workloads/pods/disruptions/
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Disruption
|
||||
id: disruption
|
||||
date: 2019-09-10
|
||||
full_link: /zh/docs/concepts/workloads/pods/disruptions/
|
||||
full_link: /docs/concepts/workloads/pods/disruptions/
|
||||
short_description: >
|
||||
An event that leads to Pod(s) going out of service
|
||||
aka:
|
||||
|
|
@ -42,4 +42,6 @@ Kubernetes terms that an _involuntary disruption_.
|
|||
See [Disruptions](/docs/concepts/workloads/pods/disruptions/) for more information.
|
||||
-->
|
||||
如果您作为一个集群操作人员，销毁了一个从属于某个应用的 Pod, Kubernetes 视之为 _自愿干扰_。如果由于节点故障
|
||||
或者影响更大区域故障的断电导致 Pod 离线，Kubrenetes 视之为 _非愿干扰_。
|
||||
或者影响更大区域故障的断电导致 Pod 离线，Kubrenetes 视之为 _非愿干扰_。
|
||||
|
||||
更多信息请查阅[Disruptions](/zh/docs/concepts/workloads/pods/disruptions/)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: docker
|
||||
title: Docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
|
|
@ -13,10 +13,10 @@ tags:
|
|||
|
||||
<!--
|
||||
---
|
||||
title: docker
|
||||
title: Docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
full_link: https://docs.docker.com/engine/
|
||||
short_description: >
|
||||
Docker is a software technology providing operating-system-level virtualization also known as containers.
|
||||
|
||||
|
|
@ -27,10 +27,10 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
Docker is a software technology providing operating-system-level virtualization also known as containers.
|
||||
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（这里特指Docker引擎） 是一种可以提供操作系统级别虚拟化（也称作{{< glossary_tooltip text="容器" term_id="container" >}}）的软件技术。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 下游(消除歧义)
|
||||
title: Downstream（下游）（消除歧义）
|
||||
id: downstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 动态卷供应
|
||||
title: Dynamic Volume Provisioning（动态卷供应）
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/dynamic-provisioning/
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Dynamic Volume Provisioning
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/dynamic-provisioning/
|
||||
full_link: /docs/concepts/storage/dynamic-provisioning
|
||||
short_description: >
|
||||
Allows users to request automatic creation of storage Volumes.
|
||||
|
||||
|
|
@ -41,4 +41,4 @@ Dynamic provisioning eliminates the need for cluster administrators to pre-provi
|
|||
-->
|
||||
|
||||
动态供应让集群管理员无需再预先供应存储。相反，它通过用户请求自动地供应存储。
|
||||
动态卷供应是基于 API 对象 {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}} 的，StorageClass 可以引用 {{< glossary_tooltip text="卷插件（Volume Plugin）" term_id="volume-plugin" >}} 提供的 {{< glossary_tooltip text="卷（Volume）" term_id="volume" >}} ，也可以引用传递给卷插件（Volume Plugin）的参数集。
|
||||
动态卷供应是基于 API 对象 {{< glossary_tooltip text="StorageClass" term_id="储存类别（storage-class）" >}} 的，StorageClass 可以引用 {{< glossary_tooltip text="卷插件（Volume Plugin）" term_id="volume-plugin" >}} 提供的 {{< glossary_tooltip text="卷（Volume）" term_id="volume" >}} ，也可以引用传递给卷插件（Volume Plugin）的参数集。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 端点切片
|
||||
title: Endpoint Slice（端点切片）
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/endpoint-slices/
|
||||
|
|
@ -14,10 +14,10 @@ tags:
|
|||
|
||||
<!--
|
||||
---
|
||||
title: Endpoint Slice
|
||||
title: EndpointSlice
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/endpoint-slices/
|
||||
full_link: /docs/concepts/services-networking/endpoint-slices/
|
||||
short_description: >
|
||||
A way to group network endpoints together with Kubernetes resources.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 端点（Endpoints）
|
||||
title: Endpoints（端点）
|
||||
id: endpoints
|
||||
date: 2020-04-23
|
||||
full_link:
|
||||
|
|
@ -23,14 +23,16 @@ short_description: >
|
|||
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 Services without selectors specified.
|
||||
The EndpointSlice resource provides a scalable and extensible alternative to Endpoints.
|
||||
Endpoints can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
|
||||
-->
|
||||
端点可以手动配置到{{< glossary_tooltip text="服务（Service）" term_id="service" >}}上，而不必设置选择算符。
|
||||
{{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} 资源为 Endpoints
|
||||
提供了一种可伸缩、可扩展的替代方案。
|
||||
端点可以手动配置到{{< 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" >}}提供了一种可伸缩、可扩展的替代方案。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 临时容器
|
||||
title: Ephemeral Container（临时容器）
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /zh/docs/concepts/workloads/pods/ephemeral-containers/
|
||||
|
|
@ -16,7 +16,7 @@ tags:
|
|||
title: Ephemeral Container
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /zh/docs/concepts/workloads/pods/ephemeral-containers/
|
||||
full_link: /docs/concepts/workloads/pods/ephemeral-containers/
|
||||
short_description: >
|
||||
A type of container type that you can temporarily run inside a Pod
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: etcd
|
||||
id: etcd
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/administer-cluster/configure-upgrade-etcd/
|
||||
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.
|
||||
|
||||
|
|
@ -35,9 +35,14 @@ tags:
|
|||
etcd 是兼具一致性和高可用性的键值数据库，可以作为保存 Kubernetes 所有集群数据的后台数据库。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Always have a backup plan for etcd's data for your Kubernetes cluster. For in-depth information on etcd, see [etcd documentation](https://etcd.io/docs).
|
||||
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 数据库通常需要有个备份计划。
|
||||
<!--
|
||||
You can find in-depth information about etcd in the official [documentation](https://etcd.io/docs/).
|
||||
-->
|
||||
|
||||
您的 Kubernetes 集群的 etcd 数据库通常需要有个备份计划。要了解 etcd 更深层次的信息，请参考 [etcd 文档](https://etcd.io/docs)。
|
||||
要了解 etcd 更深层次的信息，请参考 [etcd 文档](https://etcd.io/docs/)。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 扩展组件
|
||||
title: Extensions（扩展组件）
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Extensions
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ tags:
|
|||
title: FlexVolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#flexvolume
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
|
||||
|
||||
|
|
@ -25,17 +25,23 @@ aka:
|
|||
tags:
|
||||
- storage
|
||||
--- -->
|
||||
<!-- FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes. -->
|
||||
<!--
|
||||
FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
|
||||
-->
|
||||
Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< 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. -->
|
||||
<!--
|
||||
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/flexvolume.md)
|
||||
* [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md) -->
|
||||
<!--
|
||||
* [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](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [更多关于 Flexvolumes 的信息](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
|
||||
* [更多关于 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)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Pod 水平自动扩缩器
|
||||
title: Horizontal Pod Autoscaler（Pod 水平自动扩缩器）
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
|
|
@ -7,6 +7,7 @@ short_description: >
|
|||
Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
aka:
|
||||
- HPA
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
|
@ -16,22 +17,23 @@ tags:
|
|||
title: Horizontal Pod Autoscaler
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
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
|
||||
---
|
||||
-->
|
||||
|
||||
Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
Horizontal Pod Autoscaler（Pod 水平自动扩缩器）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
HPA is typically used with {{< glossary_tooltip text="Replication Controllers" term_id="replication-controller" >}}, {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or Replica Sets. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
|
||||
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="Replication Controllers" term_id="replication-controller" >}}、{{< glossary_tooltip text="Deployments" term_id="deployment" >}} 或者 Replica Sets 上。HPA 不能用于不支持扩缩的对象，例如 {{< 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" >}}。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 镜像
|
||||
title: Image（镜像）
|
||||
id: image
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
|
|
@ -27,10 +27,10 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
Stored instance of a container that holds a set of software needed to run an application.
|
||||
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-->
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ tags:
|
|||
title: Ingress
|
||||
id: ingress
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/services-networking/ingress/
|
||||
full_link: /docs/concepts/services-networking/ingress/
|
||||
short_description: >
|
||||
An API object that manages external access to the services in a cluster, typically HTTP.
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ tags:
|
|||
<!--more-->
|
||||
|
||||
<!--
|
||||
Ingress can provide load balancing, SSL termination and name-based virtual hosting.
|
||||
Ingress may provide load balancing, SSL termination and name-based virtual hosting.
|
||||
-->
|
||||
|
||||
Ingress 可以提供负载均衡、SSL 终结和基于名称的虚拟托管。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 初始化容器
|
||||
title: Init Container（初始化容器）
|
||||
id: init-container
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
|
|
@ -18,7 +18,7 @@ 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.
|
||||
One or more initialization containers that must run to completion before any app containers run.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -27,15 +27,15 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
One or more initialization containers that must run to completion before any app containers run.
|
||||
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.
|
||||
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）容器开始前运行完成。
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/overview.html
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/
|
||||
short_description: >
|
||||
Istio 是个开放平台（非 Kubernetes 特有），提供了一种统一的方式来集成微服务、管理流量、实施策略和汇总度量数据。
|
||||
aka:
|
||||
|
|
@ -17,7 +17,7 @@ tags:
|
|||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/overview.html
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/jobs-run-to-completion
|
||||
full_link: /zh/docs/concepts/workloads/controllers/job/
|
||||
short_description: >
|
||||
Job 是需要运行完成的确定性的或批量的任务。
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ tags:
|
|||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/jobs-run-to-completion
|
||||
full_link: /docs/concepts/workloads/controllers/job/
|
||||
short_description: >
|
||||
A finite or batch task that runs to completion.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ id: kops
|
|||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/kops/
|
||||
short_description: >
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。注意：官方仅支持 AWS，GCE 和 VMware vSphere 的支持还处于 alpha* 阶段。
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -19,7 +19,7 @@ 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. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
|
|
@ -29,13 +29,22 @@ tags:
|
|||
-->
|
||||
|
||||
<!--
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters.
|
||||
-->
|
||||
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。*注意：官方仅支持 AWS，GCE 和 VMware vSphere 的支持还处于 alpha 阶段*。
|
||||
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:
|
||||
|
||||
|
|
@ -44,7 +53,7 @@ kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护
|
|||
* 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 generate terraform manifests
|
||||
* The ability to directly provision, or to generate Terraform manifests
|
||||
-->
|
||||
|
||||
`kops` 为您的集群提供了：
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: shuffle sharding
|
||||
id: shuffle-sharding
|
||||
date: 2020-03-04
|
||||
full_link:
|
||||
short_description: >
|
||||
A technique for assigning requests to queues that provides better isolation than hashing modulo the number of queues.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Shuffle Sharding（混排切片）
|
||||
id: shuffle-sharding
|
||||
|
|
@ -28,6 +11,22 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: shuffle sharding
|
||||
id: shuffle-sharding
|
||||
date: 2020-03-04
|
||||
full_link:
|
||||
short_description: >
|
||||
A technique for assigning requests to queues that provides better isolation than hashing modulo the number of queues.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A technique for assigning requests to queues that provides better isolation than hashing modulo the number of queues.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: SIG (special interest group)
|
||||
id: sig
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
|
||||
short_description: >
|
||||
Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: SIG （特别兴趣小组）
|
||||
id: sig
|
||||
|
|
@ -28,6 +11,21 @@ tags:
|
|||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: SIG (special interest group)
|
||||
id: sig
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
|
||||
short_description: >
|
||||
Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
{{< glossary_tooltip text="Community members" term_id="member" >}} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,19 @@
|
|||
<!--
|
||||
---
|
||||
title: StatefulSet
|
||||
id: statefulset
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/statefulset/
|
||||
short_description: >
|
||||
StatefulSet 用来管理部署和伸缩一组 Pod，包括这些 Pod 的持久存储和持久标识符。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: StatefulSet
|
||||
id: statefulset
|
||||
|
|
@ -15,25 +29,8 @@ tags:
|
|||
- workload
|
||||
- storage
|
||||
---
|
||||
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: StatefulSet
|
||||
id: statefulset
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/statefulset/
|
||||
short_description: >
|
||||
StatefulSet 用来管理部署和伸缩一组 Pod，包括这些 Pod 的持久存储和持久标识符。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
Manages the deployment and scaling of a set of {{< glossary_tooltip text="Pods" term_id="pod" >}}, *and provides guarantees about the ordering and uniqueness* of these Pods.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Static Pod
|
||||
id: static-pod
|
||||
date: 2019-02-12
|
||||
full_link: /docs/tasks/configure-pod-container/static-pod/
|
||||
short_description: >
|
||||
A pod managed directly by the kubelet daemon on a specific node.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Static Pod
|
||||
id: static-pod
|
||||
|
|
@ -28,7 +11,20 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Static Pod
|
||||
id: static-pod
|
||||
date: 2019-02-12
|
||||
full_link: /docs/tasks/configure-pod-container/static-pod/
|
||||
short_description: >
|
||||
A pod managed directly by the kubelet daemon on a specific node.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A {{< glossary_tooltip text="pod" term_id="pod" >}} managed directly by the kubelet
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Storage Class
|
||||
id: storageclass
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/storage-classes
|
||||
short_description: >
|
||||
A StorageClass provides a way for administrators to describe different available storage types.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: StorageClass
|
||||
id: storageclass
|
||||
|
|
@ -31,6 +13,22 @@ tags:
|
|||
---
|
||||
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Storage Class
|
||||
id: storageclass
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/storage-classes
|
||||
short_description: >
|
||||
A StorageClass provides a way for administrators to describe different available storage types.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A StorageClass provides a way for administrators to describe different available storage types.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,19 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: sysctl
|
||||
id: sysctl
|
||||
date: 2019-02-12
|
||||
full_link: /docs/tasks/administer-cluster/sysctl-cluster/
|
||||
short_description: >
|
||||
An interface for getting and setting Unix kernel parameters
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
---
|
||||
title: sysctl
|
||||
id: sysctl
|
||||
|
|
@ -27,7 +11,20 @@ tags:
|
|||
- 工具
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: sysctl
|
||||
id: sysctl
|
||||
date: 2019-02-12
|
||||
full_link: /docs/tasks/administer-cluster/sysctl-cluster/
|
||||
short_description: >
|
||||
An interface for getting and setting Unix kernel parameters
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
`sysctl` is a semi-standardized interface for reading or changing the
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Taint
|
||||
id: taint
|
||||
date: 2019-01-11
|
||||
full_link: /docs/concepts/configuration/taint-and-toleration/
|
||||
short_description: >
|
||||
A core object consisting of three required properties: key, value, and effect. Taints prevent the scheduling of pods on nodes or node groups.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Taint（污点）
|
||||
id: taint
|
||||
|
|
@ -29,6 +11,23 @@ tags:
|
|||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Taint
|
||||
id: taint
|
||||
date: 2019-01-11
|
||||
full_link: /docs/concepts/configuration/taint-and-toleration/
|
||||
short_description: >
|
||||
A core object consisting of three required properties: key, value, and effect. Taints prevent the scheduling of pods on nodes or node groups.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A core object consisting of three required properties: key, value, and effect. Taints prevent the scheduling of {{< glossary_tooltip text="Pods" term_id="pod" >}} on {{< glossary_tooltip text="nodes" term_id="node" >}} or node groups.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Toleration
|
||||
id: toleration
|
||||
date: 2019-01-11
|
||||
full_link: /docs/concepts/scheduling-eviction/taint-and-toleration/
|
||||
short_description: >
|
||||
A core object consisting of three required properties: key, value, and effect. Tolerations enable the scheduling of pods on nodes or node groups that have a matching taint.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: toleration（容忍度）
|
||||
id: toleration
|
||||
|
|
@ -29,6 +11,22 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Toleration
|
||||
id: toleration
|
||||
date: 2019-01-11
|
||||
full_link: /docs/concepts/scheduling-eviction/taint-and-toleration/
|
||||
short_description: >
|
||||
A core object consisting of three required properties: key, value, and effect. Tolerations enable the scheduling of pods on nodes or node groups that have a matching taint.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A core object consisting of three required properties: key, value, and effect. Tolerations enable the scheduling of pods on nodes or node groups that have matching {{< glossary_tooltip text="taints" term_id="taint" >}}.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: UID
|
||||
id: uid
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/names
|
||||
short_description: >
|
||||
A Kubernetes systems-generated string to uniquely identify objects.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: UID
|
||||
id: uid
|
||||
|
|
@ -28,7 +11,20 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: UID
|
||||
id: uid
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/names
|
||||
short_description: >
|
||||
A Kubernetes systems-generated string to uniquely identify objects.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A Kubernetes systems-generated string to uniquely identify objects.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Upstream (disambiguation)
|
||||
id: upstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: core Kubernetes or the source repo from which a repo was forked.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Upstream (disambiguation)
|
||||
id: upstream
|
||||
|
|
@ -27,6 +10,22 @@ aka:
|
|||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Upstream (disambiguation)
|
||||
id: upstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: core Kubernetes or the source repo from which a repo was forked.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
May refer to: core Kubernetes or the source repo from which a repo was forked.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Volume Plugin
|
||||
id: volumeplugin
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A Volume Plugin enables integration of storage within a Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Volume Plugin（卷插件）
|
||||
id: volumeplugin
|
||||
|
|
@ -30,6 +12,22 @@ tags:
|
|||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Volume Plugin
|
||||
id: volumeplugin
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A Volume Plugin enables integration of storage within a Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A Volume Plugin enables integration of storage within a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,21 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Volume
|
||||
id: volume
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/volumes/
|
||||
short_description: >
|
||||
A directory containing data, accessible to the containers in a pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Volume（卷）
|
||||
id: volume
|
||||
|
|
@ -30,6 +12,22 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Volume
|
||||
id: volume
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/volumes/
|
||||
short_description: >
|
||||
A directory containing data, accessible to the containers in a pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
A directory containing data, accessible to the {{< glossary_tooltip text="containers" term_id="container" >}} in a {{< glossary_tooltip term_id="pod" >}}.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: WG (working group)
|
||||
id: wg
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-working-group-list
|
||||
short_description: >
|
||||
Facilitates the discussion and/or implementation of a short-lived, narrow, or decoupled project for a committee, SIG, or cross-SIG effort.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: WG (工作组)
|
||||
id: wg
|
||||
|
|
@ -28,6 +11,20 @@ tags:
|
|||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: WG (working group)
|
||||
id: wg
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-working-group-list
|
||||
short_description: >
|
||||
Facilitates the discussion and/or implementation of a short-lived, narrow, or decoupled project for a committee, SIG, or cross-SIG effort.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -1,20 +1,3 @@
|
|||
<!--
|
||||
|
||||
---
|
||||
title: Workload
|
||||
id: workloads
|
||||
date: 2019-02-13
|
||||
full_link: /docs/concepts/workloads/
|
||||
short_description: >
|
||||
A workload is an application running on Kubernetes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
-->
|
||||
|
||||
---
|
||||
title: Workload（工作负载）
|
||||
id: workloads
|
||||
|
|
@ -28,6 +11,22 @@ tags:
|
|||
- fundamental
|
||||
---
|
||||
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Workload
|
||||
id: workloads
|
||||
date: 2019-02-13
|
||||
full_link: /docs/concepts/workloads/
|
||||
short_description: >
|
||||
A workload is an application running on Kubernetes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A workload is an application running on Kubernetes.
|
||||
-->
|
||||
|
|
|
|||
Loading…
Reference in New Issue