Merge pull request #39049 from Zhuzhenghao/dns-horizontal-autoscaling
[zh-cn] sync 5 files in /task/administer-clusterpull/39079/head
Kubernetes Prow Robot
GitHub
commit
4c715d3035
|
|
@ -2,6 +2,7 @@
|
|||
title: 迁移多副本的控制面以使用云控制器管理器
|
||||
linkTitle: 迁移多副本的控制面以使用云控制器管理器
|
||||
content_type: task
|
||||
weight: 250
|
||||
---
|
||||
|
||||
<!--
|
||||
|
|
@ -11,6 +12,7 @@ reviewers:
|
|||
title: "Migrate Replicated Control Plane To Use Cloud Controller Manager"
|
||||
linkTitle: "Migrate Replicated Control Plane To Use Cloud Controller Manager"
|
||||
content_type: task
|
||||
weight: 250
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
|
@ -22,7 +24,7 @@ content_type: task
|
|||
<!--
|
||||
## Background
|
||||
|
||||
As part of the [cloud provider extraction effort](https://kubernetes.io/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/),
|
||||
As part of the [cloud provider extraction effort](/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/),
|
||||
all cloud specific controllers must be moved out of the `kube-controller-manager`.
|
||||
All existing clusters that run cloud controllers in the `kube-controller-manager` must migrate to instead run the controllers in a cloud provider specific `cloud-controller-manager`.
|
||||
|
||||
|
|
@ -32,7 +34,7 @@ For a single-node control plane, or if unavailability of controller managers can
|
|||
-->
|
||||
## 背景
|
||||
|
||||
作为[云驱动提取工作](https://kubernetes.io/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/)
|
||||
作为[云驱动提取工作](/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/)
|
||||
的一部分，所有特定于云的控制器都必须移出 `kube-controller-manager`。
|
||||
所有在 `kube-controller-manager` 中运行云控制器的现有集群必须迁移到特定于云厂商的
|
||||
`cloud-controller-manager` 中运行这些控制器。
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
title: 使用 CoreDNS 进行服务发现
|
||||
min-kubernetes-server-version: v1.9
|
||||
content_type: task
|
||||
weight: 380
|
||||
---
|
||||
|
||||
<!--
|
||||
|
|
@ -10,6 +11,7 @@ reviewers:
|
|||
title: Using CoreDNS for Service Discovery
|
||||
min-kubernetes-server-version: v1.9
|
||||
content_type: task
|
||||
weight: 380
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
|
@ -119,9 +121,9 @@ can take care of retaining the existing CoreDNS configuration automatically.
|
|||
<!--
|
||||
## Tuning CoreDNS
|
||||
|
||||
When resource utilisation is a concern, it may be useful to tune
|
||||
the configuration of CoreDNS. For more details, check out the
|
||||
[documentation on scaling CoreDNS]((https://github.com/coredns/deployment/blob/master/kubernetes/Scaling_CoreDNS.md)).
|
||||
When resource utilisation is a concern, it may be useful to tune the
|
||||
configuration of CoreDNS. For more details, check out the
|
||||
[documentation on scaling CoreDNS](https://github.com/coredns/deployment/blob/master/kubernetes/Scaling_CoreDNS.md).
|
||||
-->
|
||||
## CoreDNS 调优
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
title: 控制节点上的 CPU 管理策略
|
||||
content_type: task
|
||||
min-kubernetes-server-version: v1.26
|
||||
weight: 140
|
||||
---
|
||||
<!--
|
||||
title: Control CPU Management Policies on the Node
|
||||
|
|
@ -12,6 +13,7 @@ reviewers:
|
|||
|
||||
content_type: task
|
||||
min-kubernetes-server-version: v1.26
|
||||
weight: 140
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
title: 开发云控制器管理器
|
||||
content_type: task
|
||||
weight: 190
|
||||
---
|
||||
|
||||
<!--
|
||||
|
|
@ -10,6 +11,7 @@ reviewers:
|
|||
- wlan0
|
||||
title: Developing Cloud Controller Manager
|
||||
content_type: concept
|
||||
weight: 190
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
|
@ -48,19 +50,19 @@ Kubernetes 核心代码导入软件包来实现一个 cloud-controller-manager
|
|||
### 树外（Out of Tree）
|
||||
|
||||
<!--
|
||||
To build an out-of-tree cloud-controller-manager for your cloud, follow these steps:
|
||||
To build an out-of-tree cloud-controller-manager for your cloud:
|
||||
-->
|
||||
要为你的云环境构建一个树外（Out-of-Tree）云控制器管理器：
|
||||
|
||||
<!--
|
||||
1. Create a go package with an implementation that satisfies [cloudprovider.Interface](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go).
|
||||
2. Use [main.go in cloud-controller-manager](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/main.go) from Kubernetes core as a template for your main.go. As mentioned above, the only difference should be the cloud package that will be imported.
|
||||
3. Import your cloud package in `main.go`, ensure your package has an `init` block to run [cloudprovider.RegisterCloudProvider](https://github.com/kubernetes/cloud-provider/blob/master/plugins.go).
|
||||
2. Use [`main.go` in cloud-controller-manager](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/main.go) from Kubernetes core as a template for your `main.go`. As mentioned above, the only difference should be the cloud package that will be imported.
|
||||
3. Import your cloud package in `main.go`, ensure your package has an `init` block to run [`cloudprovider.RegisterCloudProvider`](https://github.com/kubernetes/cloud-provider/blob/master/plugins.go).
|
||||
-->
|
||||
1. 使用满足 [`cloudprovider.Interface`](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go)
|
||||
接口的实现来创建一个 Go 语言包。
|
||||
2. 使用来自 Kubernetes 核心代码库的
|
||||
[cloud-controller-manager 中的 main.go](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/main.go)
|
||||
[cloud-controller-manager 中的 `main.go`](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/main.go)
|
||||
作为 `main.go` 的模板。如上所述，唯一的区别应该是将导入的云包不同。
|
||||
3. 在 `main.go` 中导入你的云包，确保你的包有一个 `init` 块来运行
|
||||
[`cloudprovider.RegisterCloudProvider`](https://github.com/kubernetes/cloud-provider/blob/master/plugins.go)。
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
title: 自定义 DNS 服务
|
||||
content_type: task
|
||||
min-kubernetes-server-version: v1.12
|
||||
weight: 160
|
||||
---
|
||||
<!--
|
||||
reviewers:
|
||||
|
|
@ -10,6 +11,7 @@ reviewers:
|
|||
title: Customizing DNS Service
|
||||
content_type: task
|
||||
min-kubernetes-server-version: v1.12
|
||||
weight: 160
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
|
@ -169,7 +171,7 @@ Corefile 配置包括以下 CoreDNS [插件](https://coredns.io/plugins/)：
|
|||
<!--
|
||||
* [errors](https://coredns.io/plugins/errors/): Errors are logged to stdout.
|
||||
* [health](https://coredns.io/plugins/health/): Health of CoreDNS is reported to
|
||||
`http://localhost:8080/health`. In this extended syntax `lameduck` will make theuprocess
|
||||
`http://localhost:8080/health`. In this extended syntax `lameduck` will make the process
|
||||
unhealthy then wait for 5 seconds before the process is shut down.
|
||||
* [ready](https://coredns.io/plugins/ready/): An HTTP endpoint on port 8181 will return 200 OK,
|
||||
when all plugins that are able to signal readiness have done so.
|
||||
|
|
|
|||
Loading…
Reference in New Issue