Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 Misty Linville
|
5294779969 | ||
|
Misty Linville
|
5f30e7d4c3 |
@@ -1,10 +1,19 @@
|
||||
# Reviewers can /lgtm /approve but not sufficient for auto-merge without an
|
||||
# approver
|
||||
reviewers:
|
||||
- sig-docs-en-reviews
|
||||
|
||||
- zhangxiaoyu-zidif
|
||||
- xiangpengzhao
|
||||
- stewart-yu
|
||||
- Rajakavitha1
|
||||
# Approvers have all the ability of reviewers but their /approve makes
|
||||
# auto-merge happen if a /lgtm exists, or vice versa, or they can do both
|
||||
# No need for approvers to also be listed as reviewers
|
||||
approvers:
|
||||
- sig-docs-en-owners
|
||||
- heckj
|
||||
- bradamant3
|
||||
- bradtopol
|
||||
- steveperry-53
|
||||
- zacharysarah
|
||||
- chenopis
|
||||
- mistyhacks
|
||||
- tengqm
|
||||
|
||||
+7
-83
@@ -41,11 +41,9 @@ aliases:
|
||||
- chrislovecnm
|
||||
- mfburnett
|
||||
sig-azure: #Microsoft Azure
|
||||
- andyzhangx
|
||||
- feiskyer
|
||||
- justaugustus
|
||||
- karataliu
|
||||
- khenidak
|
||||
- slack
|
||||
- colemickens
|
||||
- jdumars
|
||||
sig-big-data: #GH: sig-big-data-pr-reviews
|
||||
- foxish
|
||||
sig-cli: #Team: CLI; GH: sig-cli-pr-reviews; e.g. kubectl
|
||||
@@ -63,25 +61,11 @@ aliases:
|
||||
- smarterclayton
|
||||
- soltysh
|
||||
- sttts
|
||||
sig-cluster-lifecycle-kubeadm-approvers: # Approving changes to kubeadm documentation
|
||||
sig-cluster-lifecycle: #GH: sig-cluster-lifecycle-pr-reviews
|
||||
- timothysc
|
||||
- lukemarsden
|
||||
- luxas
|
||||
- roberthbailey
|
||||
- fabriziopandini
|
||||
sig-cluster-lifecycle-kubeadm-reviewers: # Reviewing kubeadm documentation
|
||||
- timothysc
|
||||
- lukemarsden
|
||||
- luxas
|
||||
- roberthbailey
|
||||
- fabriziopandini
|
||||
- kad
|
||||
- xiangpengzhao
|
||||
- stealthybox
|
||||
- liztio
|
||||
- chuckha
|
||||
- detiber
|
||||
- dixudx
|
||||
- fabriziopandini
|
||||
sig-cluster-ops:
|
||||
- zehicle
|
||||
- jdumars
|
||||
@@ -97,71 +81,12 @@ aliases:
|
||||
- apelisse
|
||||
- grodrigues3
|
||||
- spxtr
|
||||
sig-docs: #Team: documentation; GH: sig-docs-maintainers
|
||||
sig-docs: #Team: documentation; GH: sig-docs-pr-reviews
|
||||
- bradamant3
|
||||
- bradtopol
|
||||
- chenopis
|
||||
- jaredbhatti
|
||||
- kbarnard10
|
||||
- mistyhacks
|
||||
- ryanmcginnis
|
||||
- steveperry-53
|
||||
- tengqm
|
||||
- tfogo
|
||||
- xiangpengzhao
|
||||
- zacharysarah
|
||||
- zhangxiaoyu-zidif
|
||||
- zparnold
|
||||
sig-docs-en-owners: #Team: Documentation; GH: sig-docs-en-owners
|
||||
- bradamant3
|
||||
- bradtopol
|
||||
- chenopis
|
||||
- jaredbhatti
|
||||
- kbarnard10
|
||||
- mistyhacks
|
||||
- ryanmcginnis
|
||||
- steveperry-53
|
||||
- stewart-yu
|
||||
- tengqm
|
||||
- tfogo
|
||||
- zacharysarah
|
||||
- zparnold
|
||||
sig-docs-en-reviews: #Team: Documentation; GH: sig-docs-pr-reviews
|
||||
- jimangel
|
||||
- rajakavitha1
|
||||
- stewart-yu
|
||||
- xiangpengzhao
|
||||
- zhangxiaoyu
|
||||
sig-docs-ja-owners: #Team: Japanese docs localization; GH: sig-docs-ja-owners
|
||||
- cstoku
|
||||
- nasa9084
|
||||
- tnir
|
||||
sig-docs-ja-reviews: #Team: Japanese docs PR reviews; GH:sig-docs-ja-reviews
|
||||
- cstoku
|
||||
- makocchi-git
|
||||
- MasayaAoyama
|
||||
- nasa9084
|
||||
- tnir
|
||||
sig-docs-ko-owners: #Team Korean docs localization; GH: sig-docs-ko-owners
|
||||
- ClaudiaJKang
|
||||
- gochist
|
||||
sig-docs-ko-reviews: #Team Korean docs reviews; GH: sig-docs-ko-reviews
|
||||
- ClaudiaJKang
|
||||
- gochist
|
||||
- ianychoi
|
||||
sig-docs-zh-owners: #Team Chinese docs localization; GH: sig-docs-zh-owners
|
||||
- dchen1107
|
||||
- haibinxie
|
||||
- hanjiayao
|
||||
- lichuqiang
|
||||
- tengqm
|
||||
- xiangpengzhao
|
||||
- zhangxiaoyu-zidif
|
||||
sig-docs-zh-reviews: #Team Chinese docs reviews; GH: sig-docs-zh-reviews
|
||||
- idealhack
|
||||
- tengqm
|
||||
- xiangpengzhao
|
||||
- zhangxiaoyu-zidif
|
||||
- heckj
|
||||
sig-federation: #Team: Federation; e.g. Federated Clusters
|
||||
- csbell
|
||||
sig-gcp: #Google Cloud Platform; GH: sig-gcp-pr-reviews
|
||||
@@ -272,4 +197,3 @@ aliases:
|
||||
- floreks
|
||||
sig-windows:
|
||||
- michmike
|
||||
|
||||
+37
-83
@@ -7,7 +7,7 @@ enableRobotsTXT = true
|
||||
|
||||
disableKinds = ["taxonomy", "taxonomyTerm"]
|
||||
|
||||
ignoreFiles = [ "^OWNERS$", "README[-]+[a-z]*\\.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ]
|
||||
ignoreFiles = [ "^OWNERS$", "README.md", "^node_modules$" ]
|
||||
|
||||
contentDir = "content/en"
|
||||
|
||||
@@ -19,12 +19,6 @@ pygmentsUseClasses = false
|
||||
# See https://help.farbox.com/pygments.html
|
||||
pygmentsStyle = "emacs"
|
||||
|
||||
# Enable Git variables like commit, lastmod
|
||||
enableGitInfo = true
|
||||
|
||||
# Norwegian ("no") is sometimes but not currently used for testing.
|
||||
disableLanguages = ["no"]
|
||||
|
||||
[blackfriday]
|
||||
hrefTargetBlank = true
|
||||
fractions = false
|
||||
@@ -33,93 +27,71 @@ fractions = false
|
||||
date = ["date", ":filename", "publishDate", "lastmod"]
|
||||
|
||||
[permalinks]
|
||||
blog = "/:section/:year/:month/:day/:slug/"
|
||||
blog = "/:section/:year/:month/:day/:slug/"
|
||||
|
||||
# Be explicit about the output formats. We (currently) only want an RSS feed for the home page.
|
||||
[outputs]
|
||||
home = [ "HTML", "RSS", "HEADERS" ]
|
||||
home = [ "HTML", "RSS"]
|
||||
page = [ "HTML"]
|
||||
section = [ "HTML"]
|
||||
|
||||
# Add a "text/netlify" media type for auto-generating the _headers file
|
||||
[mediaTypes]
|
||||
[mediaTypes."text/netlify"]
|
||||
delimiter = ""
|
||||
|
||||
[outputFormats]
|
||||
[outputFormats.RSS]
|
||||
baseName = "feed"
|
||||
|
||||
# _headers file output (uses the template at layouts/index.headers)
|
||||
[outputFormats.HEADERS]
|
||||
mediatype = "text/netlify"
|
||||
baseName = "_headers"
|
||||
isPlainText = true
|
||||
notAlternative = true
|
||||
|
||||
[params]
|
||||
|
||||
time_format_blog = "Monday, January 02, 2006"
|
||||
description = "Production-Grade Container Orchestration"
|
||||
showedit = true
|
||||
|
||||
latest = "v1.15"
|
||||
latest = "v1.11"
|
||||
|
||||
fullversion = "v1.11.10"
|
||||
fullversion = "v1.11.0"
|
||||
version = "v1.11"
|
||||
githubbranch = "v1.11.10"
|
||||
docsbranch = "release-1.11"
|
||||
deprecated = true
|
||||
githubbranch = "master"
|
||||
docsbranch = "master"
|
||||
deprecated = false
|
||||
currentUrl = "https://kubernetes.io/docs/home/"
|
||||
nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/"
|
||||
nextUrl = "http://kubernetes-io-vnext-staging.netlify.com/"
|
||||
githubWebsiteRepo = "github.com/kubernetes/website"
|
||||
githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website"
|
||||
|
||||
[[params.versions]]
|
||||
fullversion = "v1.15.0"
|
||||
version = "v1.15"
|
||||
githubbranch = "v1.15.0"
|
||||
docsbranch = "release-1.15"
|
||||
fullversion = "v1.11.0"
|
||||
version = "v1.11"
|
||||
githubbranch = "v1.11.0"
|
||||
docsbranch = "release-1.11"
|
||||
url = "https://kubernetes.io"
|
||||
|
||||
[params.pushAssets]
|
||||
css = [
|
||||
"callouts",
|
||||
"styles",
|
||||
"custom-jekyll/tags"
|
||||
]
|
||||
js = [
|
||||
"custom-jekyll/tags",
|
||||
"script"
|
||||
]
|
||||
[[params.versions]]
|
||||
fullversion = "v1.10.3"
|
||||
version = "v1.10"
|
||||
githubbranch = "v1.10.3"
|
||||
docsbranch = "release-1.10"
|
||||
url = "https://kubernetes.io"
|
||||
|
||||
[[params.versions]]
|
||||
fullversion = "v1.14.3"
|
||||
version = "v1.14"
|
||||
githubbranch = "v1.14.3"
|
||||
docsbranch = "release-1.14"
|
||||
url = "https://v1-14.docs.kubernetes.io"
|
||||
fullversion = "v1.9.7"
|
||||
version = "v1.9"
|
||||
githubbranch = "v1.9.7"
|
||||
docsbranch = "release-1.9"
|
||||
url = "https://v1-9.docs.kubernetes.io"
|
||||
|
||||
[[params.versions]]
|
||||
fullversion = "v1.13.7"
|
||||
version = "v1.13"
|
||||
githubbranch = "v1.13.7"
|
||||
docsbranch = "release-1.13"
|
||||
url = "https://v1-13.docs.kubernetes.io"
|
||||
fullversion = "v1.8.4"
|
||||
version = "v1.8"
|
||||
githubbranch = "v1.8.4"
|
||||
docsbranch = "release-1.8"
|
||||
url = "https://v1-8.docs.kubernetes.io"
|
||||
|
||||
[[params.versions]]
|
||||
fullversion = "v1.12.9"
|
||||
version = "v1.12"
|
||||
githubbranch = "v1.12.9"
|
||||
docsbranch = "release-1.12"
|
||||
url = "https://v1-12.docs.kubernetes.io"
|
||||
fullversion = "v1.7.6"
|
||||
version = "v1.7"
|
||||
githubbranch = "v1.7.6"
|
||||
docsbranch = "release-1.7"
|
||||
url = "https://v1-7.docs.kubernetes.io"
|
||||
|
||||
[[params.versions]]
|
||||
fullversion = "v1.11.10"
|
||||
version = "v1.11"
|
||||
githubbranch = "v1.11.10"
|
||||
docsbranch = "release-1.11"
|
||||
url = "https://v1-11.docs.kubernetes.io"
|
||||
|
||||
# Language definitions.
|
||||
|
||||
@@ -130,29 +102,11 @@ description = "Production-Grade Container Orchestration"
|
||||
languageName ="English"
|
||||
# Weight used for sorting.
|
||||
weight = 1
|
||||
|
||||
[languages.zh]
|
||||
[languages.cn]
|
||||
title = "Kubernetes"
|
||||
description = "Production-Grade Container Orchestration"
|
||||
languageName = "中文 Chinese"
|
||||
languageName ="Chinese"
|
||||
weight = 2
|
||||
contentDir = "content/zh"
|
||||
contentDir = "content/cn"
|
||||
|
||||
[languages.ko]
|
||||
title = "Kubernetes"
|
||||
description = "Production-Grade Container Orchestration"
|
||||
languageName = "한국어 Korean"
|
||||
weight = 3
|
||||
contentDir = "content/ko"
|
||||
|
||||
[languages.no]
|
||||
title = "Kubernetes"
|
||||
description = "Production-Grade Container Orchestration"
|
||||
languageName ="Norsk"
|
||||
weight = 4
|
||||
contentDir = "content/no"
|
||||
|
||||
[languages.no.params]
|
||||
time_format_blog = "02.01.2006"
|
||||
# A list of language codes to look for untranslated content, ordered from left to right.
|
||||
language_alternatives = ["en"]
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
# This is the directory for English source content.
|
||||
# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
|
||||
|
||||
reviewers:
|
||||
- sig-docs-en-reviews
|
||||
|
||||
approvers:
|
||||
- sig-docs-en-owners
|
||||
|
||||
labels:
|
||||
- language/en
|
||||
@@ -111,27 +111,12 @@ object for each such mapping that they want.
|
||||
PriorityClass also has two optional fields: `globalDefault` and `description`.
|
||||
The `globalDefault` field indicates that the value of this PriorityClass should
|
||||
be used for Pods without a `priorityClassName`. Only one PriorityClass with
|
||||
`globalDefault` set to true should exist in the system. If there is more than one
|
||||
PriorityClass with `globalDefault` set to true, the value of the smallest
|
||||
of those PriorityClasses is used as the default priority. If there is no PriorityClass
|
||||
`globalDefault` set to true can exist in the system. If there is no PriorityClass
|
||||
with `globalDefault` set, the priority of Pods with no `priorityClassName` is zero.
|
||||
|
||||
The `description` field is an arbitrary string. It is meant to tell users of
|
||||
the cluster when they should use this PriorityClass.
|
||||
|
||||
Kubernetes comes with two predefined PriorityClasses: `system-node-critical`, and
|
||||
`system-cluster-critical`. The former has the highest priority and is used for critical
|
||||
system Pods that must run on all or most of the nodes and should never
|
||||
be preempted. The latter is used for system critical Pods that must always
|
||||
run in a cluster, but they can be terminated on one node and started on a
|
||||
different node.
|
||||
|
||||
{{< note >}}
|
||||
**Note**: You should never use these PriorityClasses that are dedicated to
|
||||
system components for non-system Pods. Otherwise, Pods with such high priorities
|
||||
might preempt system critical components, causing disruption of cluster services.
|
||||
{{< /note >}}
|
||||
|
||||
### Notes about PodPriority and existing clusters
|
||||
- If you upgrade your existing cluster and enable this feature, the priority
|
||||
of your existing Pods is effectively zero.
|
||||
@@ -147,13 +132,13 @@ that use the name of the deleted PriorityClass.
|
||||
### Example PriorityClass
|
||||
|
||||
```yaml
|
||||
apiVersion: scheduling.k8s.io/v1beta1
|
||||
apiVersion: scheduling.k8s.io/v1alpha1
|
||||
kind: PriorityClass
|
||||
metadata:
|
||||
name: high-priority
|
||||
value: 1000000
|
||||
globalDefault: false
|
||||
description: "This priority class should be used for XYZ service Pods only."
|
||||
description: "This priority class should be used for XYZ service pods only."
|
||||
```
|
||||
|
||||
## Pod priority
|
||||
@@ -257,7 +242,7 @@ preceding question must be yes. If the answer is no, the Node is not considered
|
||||
for preemption.
|
||||
{{< /note >}}
|
||||
|
||||
If a pending Pod has inter-Pod affinity to one or more of the lower-priority Pods
|
||||
If a pending Pod has inter-pod affinity to one or more of the lower-priority Pods
|
||||
on the Node, the inter-Pod affinity rule cannot be satisfied in the absence of those
|
||||
lower-priority Pods. In this case, the scheduler does not preempt any Pods on the
|
||||
Node. Instead, it looks for another Node. The scheduler might find a suitable Node
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -90,7 +90,7 @@ kubeadm init [flags]
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--kubernetes-version string Default: "stable-1.11"</td>
|
||||
<td colspan="2">--kubernetes-version string Default: "stable-1.10"</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">Choose a specific Kubernetes version for the control plane.</td>
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
# This is the localization project for Japanese.
|
||||
# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
|
||||
|
||||
reviewers:
|
||||
- sig-docs-ja-reviews
|
||||
|
||||
approvers:
|
||||
- sig-docs-ja-owners
|
||||
|
||||
labels:
|
||||
- language/ja
|
||||
@@ -1,11 +0,0 @@
|
||||
# This is the localization project for Korean.
|
||||
# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
|
||||
|
||||
reviewers:
|
||||
- sig-docs-ko-reviews
|
||||
|
||||
approvers:
|
||||
- sig-docs-ko-owners
|
||||
|
||||
labels:
|
||||
- language/ko
|
||||
@@ -1,11 +0,0 @@
|
||||
# This is the localization project for Chinese.
|
||||
# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
|
||||
|
||||
reviewers:
|
||||
- sig-docs-zh-reviews
|
||||
|
||||
approvers:
|
||||
- sig-docs-zh-owners
|
||||
|
||||
labels:
|
||||
- language/zh
|
||||
@@ -1,117 +0,0 @@
|
||||
<!-- ---
|
||||
title: Concepts
|
||||
main_menu: true
|
||||
content_template: templates/concept
|
||||
weight: 40
|
||||
--- -->
|
||||
|
||||
---
|
||||
title: 概念
|
||||
main_menu: true
|
||||
content_template: templates/concept
|
||||
weight: 40
|
||||
---
|
||||
|
||||
{{% capture overview %}}
|
||||
|
||||
<!-- The Concepts section helps you learn about the parts of the Kubernetes system and the abstractions Kubernetes uses to represent your cluster, and helps you obtain a deeper understanding of how Kubernetes works. -->
|
||||
|
||||
概念部分可以帮助你了解 Kubernetes 的各个组成部分以及 Kubernetes 用来表示集群的一些抽象概念，并帮助你更加深入的理解 Kubernetes 是如何工作的。
|
||||
|
||||
<!-- ## Overview -->
|
||||
|
||||
## 概述
|
||||
|
||||
<!-- To work with Kubernetes, you use *Kubernetes API objects* to describe your cluster's *desired state*: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by creating objects using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. -->
|
||||
|
||||
要使用 Kubernetes，你需要用 *Kubernetes API 对象*来描述集群的*预期状态（desired state）*：包括你需要运行的应用或者负载，它们使用的镜像、副本数，以及所需网络和磁盘资源等等。你可以使用命令行工具 `kubectl` 来调用 Kubernetes API 创建对象，通过所创建的这些对象来配置预期状态。你也可以直接调用 Kubernetes API 和集群进行交互，设置或者修改预期状态。
|
||||
|
||||
<!-- Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kubernetes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of a collection of processes running on your cluster: -->
|
||||
|
||||
一旦你设置了你所需的目标状态，*Kubernetes 控制面（control plane）* 会促成集群的当前状态符合其预期状态。为此，Kubernetes 会自动执行各类任务，比如运行或者重启容器、调整给定应用的副本数等等。Kubernetes 控制面由一组运行在集群上的进程组成：
|
||||
|
||||
<!-- * The **Kubernetes Master** is a collection of three processes that run on a single node in your cluster, which is designated as the master node. Those processes are: [kube-apiserver](/docs/admin/kube-apiserver/), [kube-controller-manager](/docs/admin/kube-controller-manager/) and [kube-scheduler](/docs/admin/kube-scheduler/).
|
||||
* Each individual non-master node in your cluster runs two processes:
|
||||
* **[kubelet](/docs/admin/kubelet/)**, which communicates with the Kubernetes Master.
|
||||
* **[kube-proxy](/docs/admin/kube-proxy/)**, a network proxy which reflects Kubernetes networking services on each node. -->
|
||||
|
||||
* **Kubernetes 主控组件（Master）** 包含三个进程，都运行在集群中的某个节上，通常这个节点被称为 master 节点。这些进程包括：[kube-apiserver](/docs/admin/kube-apiserver/)、[kube-controller-manager](/docs/admin/kube-controller-manager/)和[kube-scheduler](/docs/admin/kube-scheduler/)。
|
||||
* 集群中的每个非 master 节点都运行两个进程：
|
||||
* **[kubelet](/docs/admin/kubelet/)**，和 Kubernetes 主控组件通信。
|
||||
* **[kube-proxy](/docs/admin/kube-proxy/)**，一种网络代理，将 Kubernetes 的网络服务代理到每个节点上。
|
||||
|
||||
<!-- ## Kubernetes Objects -->
|
||||
|
||||
## Kubernetes 对象
|
||||
|
||||
<!-- Kubernetes contains a number of abstractions that represent the state of your system: deployed containerized applications and workloads, their associated network and disk resources, and other information about what your cluster is doing. These abstractions are represented by objects in the Kubernetes API; see the [Kubernetes Objects overview](/docs/concepts/abstractions/overview/) for more details. -->
|
||||
|
||||
Kubernetes 包含若干抽象用来表示系统状态，包括：已部署的容器化应用和负载、与它们相关的网络和磁盘资源以及有关集群正在运行的其他操作的信息。这些抽象使用 Kubernetes API 对象来表示。参阅 [Kubernetes对象概述](/docs/concepts/abstractions/overview/)以了解详细信息。
|
||||
|
||||
<!-- The basic Kubernetes objects include: -->
|
||||
|
||||
基本的 Kubernetes 对象包括：
|
||||
|
||||
* [Pod](/docs/concepts/workloads/pods/pod-overview/)
|
||||
* [Service](/docs/concepts/services-networking/service/)
|
||||
* [Volume](/docs/concepts/storage/volumes/)
|
||||
* [Namespace](/docs/concepts/overview/working-with-objects/namespaces/)
|
||||
|
||||
<!-- In addition, Kubernetes contains a number of higher-level abstractions called Controllers. Controllers build upon the basic objects, and provide additional functionality and convenience features. They include: -->
|
||||
|
||||
另外，Kubernetes 包含大量的被称作*控制器（controllers）*的高级抽象。控制器基于基本对象构建并提供额外的功能和方便使用的特性。具体包括：
|
||||
|
||||
* [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/)
|
||||
* [Deployment](/docs/concepts/workloads/controllers/deployment/)
|
||||
* [StatefulSet](/docs/concepts/workloads/controllers/statefulset/)
|
||||
* [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)
|
||||
* [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)
|
||||
|
||||
<!-- ## Kubernetes Control Plane -->
|
||||
|
||||
## Kubernetes 控制面
|
||||
|
||||
<!-- The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. The Control Plane maintains a record of all of the Kubernetes Objects in the system, and runs continuous control loops to manage those objects' state. At any given time, the Control Plane's control loops will respond to changes in the cluster and work to make the actual state of all the objects in the system match the desired state that you provided. -->
|
||||
|
||||
关于 Kubernetes 控制平面的各个部分，（如 Kubernetes 主控组件和 kubelet 进程，管理着 Kubernetes 如何与你的集群进行通信。控制平面维护着系统中所有的 Kubernetes 对象的状态记录，并且通过连续的控制循环来管理这些对象的状态。在任一的给定时间点，控制面的控制环都能响应集群中的变化，并且让系统中所有对象的实际状态与你提供的预期状态相匹配。
|
||||
|
||||
<!-- For example, when you use the Kubernetes API to create a Deployment object, you provide a new desired state for the system. The Kubernetes Control Plane records that object creation, and carries out your instructions by starting the required applications and scheduling them to cluster nodes--thus making the cluster's actual state match the desired state. -->
|
||||
|
||||
比如， 当你通过 Kubernetes API 创建一个 Deployment 对象，你就为系统增加了一个新的目标状态。Kubernetes 控制平面记录着对象的创建，并启动必要的应用然后将它们调度至集群某个节点上来执行你的指令，以此来保持集群的实际状态和目标状态的匹配。
|
||||
|
||||
<!-- ### Kubernetes Master -->
|
||||
|
||||
### Kubernetes Master 节点
|
||||
|
||||
<!-- The Kubernetes master is responsible for maintaining the desired state for your cluster. When you interact with Kubernetes, such as by using the `kubectl` command-line interface, you're communicating with your cluster's Kubernetes master. -->
|
||||
|
||||
Kubernetes master 节点负责维护集群的目标状态。当你要与 Kubernetes 通信时，使用如 `kubectl` 的命令行工具，就可以直接与 Kubernetes master 节点进行通信。
|
||||
|
||||
<!-- > The "master" refers to a collection of processes managing the cluster state. Typically these processes are all run on a single node in the cluster, and this node is also referred to as the master. The master can also be replicated for availability and redundancy. -->
|
||||
|
||||
> "master" 是指管理集群状态的一组进程的集合。通常这些进程都跑在集群中一个单独的节点上，并且这个节点被称为 master 节点。master 节点也可以扩展副本数，来获取更好的性能及冗余。
|
||||
|
||||
<!-- ### Kubernetes Nodes -->
|
||||
|
||||
### Kubernetes Node 节点
|
||||
|
||||
<!-- The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. The Kubernetes master controls each node; you'll rarely interact with nodes directly. -->
|
||||
|
||||
集群中的 node 节点（虚拟机、物理机等等）都是用来运行你的应用和云工作流的机器。Kubernetes master 节点控制所有 node 节点；你很少需要和 node 节点进行直接通信。
|
||||
|
||||
<!-- #### Object Metadata -->
|
||||
|
||||
#### 对象元数据
|
||||
|
||||
|
||||
* [注释](/docs/concepts/overview/working-with-objects/annotations/)
|
||||
|
||||
<!-- ### what's next -->
|
||||
|
||||
### 下一步
|
||||
|
||||
<!-- If you would like to write a concept page, see
|
||||
[Using Page Templates](/docs/home/contribute/page-templates/)
|
||||
for information about the concept page type and the concept template. -->
|
||||
|
||||
如果你想编写一个概念页面，请参阅[使用页面模板](/docs/home/contribute/page-templates/)获取更多有关概念页面类型和概念模板的信息。
|
||||
@@ -4,7 +4,7 @@
|
||||
<div class="content deprecation-warning">
|
||||
<h3>
|
||||
Documentation for Kubernetes {{ .Page.Param "version" }} is no longer actively maintained. The version you are currently viewing is a static snapshot.
|
||||
For up-to-date documentation, see the <a href="{{ .Site.Params.currentUrl }}">latest</a> version.
|
||||
For up-to-date documentation, see the <a href="{{ .Params.currentUrl }}">latest</a> version.
|
||||
</h3>
|
||||
</div>
|
||||
</main>
|
||||
|
||||
@@ -24,7 +24,7 @@ Imported docs must follow these guidelines:
|
||||
From within this directory, run the following command:
|
||||
|
||||
```
|
||||
./update-imported-docs <config.yaml>
|
||||
+./update-imported-docs-[linux|macos] <config.yaml>
|
||||
```
|
||||
|
||||
The output should look similar to the following:
|
||||
|
||||
@@ -4,5 +4,5 @@ repos:
|
||||
branch: master
|
||||
gen-absolute-links: true
|
||||
files:
|
||||
- src: CHANGELOG-1.10.md
|
||||
dst: docs/imported/release/notes.md
|
||||
- src: CHANGELOG-1.11.md
|
||||
dst: content/en/docs/imported/release/notes.md
|
||||
|
||||
Reference in New Issue
Block a user