Merge pull request #29277 from tengqm/zh-prod-env
[zh] Translate production environment
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
79bb314051
|
|
@ -1,4 +1,638 @@
|
|||
---
|
||||
title: 生产环境
|
||||
weight: 30
|
||||
no_list: true
|
||||
---
|
||||
|
||||
<!-- overview -->
|
||||
|
||||
<!--
|
||||
A production-quality Kubernetes cluster requires planning and preparation.
|
||||
If your Kubernetes cluster is to run critical workloads, it must be configured to be resilient.
|
||||
This page explains steps you can take to set up a production-ready cluster,
|
||||
or to uprate an existing cluster for production use.
|
||||
If you're already familiar with production setup and want the links, skip to
|
||||
[What's next](#what-s-next).
|
||||
-->
|
||||
生产质量的 Kubernetes 集群需要规划和准备。
|
||||
如果你的 Kubernetes 集群是用来运行关键负载的，该集群必须被配置为弹性的（Resilient）。
|
||||
本页面阐述你在安装生产就绪的集群或将现有集群升级为生产用途时可以遵循的步骤。
|
||||
如果你已经熟悉生产环境安装，因此只关注一些链接，则可以跳到[接下来](#what-s-next)节。
|
||||
|
||||
<!-- body -->
|
||||
|
||||
<!--
|
||||
## Production considerations
|
||||
|
||||
Typically, a production Kubernetes cluster environment has more requirements than a
|
||||
personal learning, development, or test environment Kubernetes. A production environment may require
|
||||
secure access by many users, consistent availability, and the resources to adapt
|
||||
to changing demands.
|
||||
-->
|
||||
## 生产环境考量 {#production-considerations}
|
||||
|
||||
通常，一个生产用 Kubernetes 集群环境与个人学习、开发或测试环境所使用的
|
||||
Kubernetes 相比有更多的需求。生产环境可能需要被很多用户安全地访问，需要
|
||||
提供一致的可用性，以及能够与需求变化相适配的资源。
|
||||
|
||||
<!--
|
||||
As you decide where you want your production Kubernetes environment to live
|
||||
(on premises or in a cloud) and the amount of management you want to take
|
||||
on or hand to others, consider how your requirements for a Kubernetes cluster
|
||||
are influenced by the following issues:
|
||||
-->
|
||||
在你决定在何处运行你的生产用 Kubernetes 环境（在本地或者在云端），以及
|
||||
你希望承担或交由他人承担的管理工作量时，需要考察以下因素如何影响你对
|
||||
Kubernetes 集群的需求：
|
||||
|
||||
<!--
|
||||
- *Availability*: A single-machine Kubernetes [learning environment](/docs/setup/#learning-environment)
|
||||
has a single point of failure. Creating a highly available cluster means considering:
|
||||
- Separating the control plane from the worker nodes.
|
||||
- Replicating the control plane components on multiple nodes.
|
||||
- Load balancing traffic to the cluster’s {{< glossary_tooltip term_id="kube-apiserver" text="API server" >}}.
|
||||
- Having enough worker nodes available, or able to quickly become available, as changing workloads warrant it.
|
||||
-->
|
||||
- *可用性*：一个单机的 Kubernetes [学习环境](/zh/docs/setup/#学习环境)
|
||||
具有单点失效特点。创建高可用的集群则意味着需要考虑：
|
||||
- 将控制面与工作节点分开
|
||||
- 在多个节点上提供控制面组件的副本
|
||||
- 为针对集群的 {{< glossary_tooltip term_id="kube-apiserver" text="API 服务器" >}}
|
||||
的流量提供负载均衡
|
||||
- 随着负载的合理需要，提供足够的可用的（或者能够迅速变为可用的）工作节点
|
||||
|
||||
<!--
|
||||
- *Scale*: If you expect your production Kubernetes environment to receive a stable amount of
|
||||
demand, you might be able to set up for the capacity you need and be done. However,
|
||||
if you expect demand to grow over time or change dramatically based on things like
|
||||
season or special events, you need to plan how to scale to relieve increased
|
||||
pressure from more requests to the control plane and worker nodes or scale down to reduce unused
|
||||
resources.
|
||||
-->
|
||||
- *规模*：如果你预期你的生产用 Kubernetes 环境要承受固定量的请求，
|
||||
你可能可以针对所需要的容量来一次性完成安装。
|
||||
不过，如果你预期服务请求会随着时间增长，或者因为类似季节或者特殊事件的
|
||||
原因而发生剧烈变化，你就需要规划如何处理请求上升时对控制面和工作节点
|
||||
的压力，或者如何缩减集群规模以减少未使用资源的消耗。
|
||||
|
||||
<!--
|
||||
- *Security and access management*: You have full admin privileges on your own
|
||||
Kubernetes learning cluster. But shared clusters with important workloads, and
|
||||
more than one or two users, require a more refined approach to who and what can
|
||||
access cluster resources. You can use role-based access control
|
||||
([RBAC](/docs/reference/access-authn-authz/rbac/)) and other
|
||||
security mechanisms to make sure that users and workloads can get access to the
|
||||
resources they need, while keeping workloads, and the cluster itself, secure.
|
||||
You can set limits on the resources that users and workloads can access
|
||||
by managing [policies](/docs/concepts/policy/) and
|
||||
[container resources](/docs/concepts/configuration/manage-resources-containers/).
|
||||
-->
|
||||
- *安全性与访问管理*：在你自己的学习环境 Kubernetes 集群上，你拥有完全的管理员特权。
|
||||
但是针对运行着重要工作负载的共享集群，用户账户不止一两个时，就需要更细粒度
|
||||
的方案来确定谁或者哪些主体可以访问集群资源。
|
||||
你可以使用基于角色的访问控制（[RBAC](/zh/docs/reference/access-authn-authz/rbac/)）
|
||||
和其他安全机制来确保用户和负载能够访问到所需要的资源，同时确保工作负载及集群
|
||||
自身仍然是安全的。
|
||||
你可以通过管理[策略](/zh/docs/concets/policy/)和
|
||||
[容器资源](/zh/docs/concepts/configuration/manage-resources-containers)来
|
||||
针对用户和工作负载所可访问的资源设置约束，
|
||||
|
||||
<!--
|
||||
Before building a Kubernetes production environment on your own, consider
|
||||
handing off some or all of this job to
|
||||
[Turnkey Cloud Solutions](/docs/setup/production-environment/turnkey-solutions/)
|
||||
providers or other [Kubernetes Partners](https://kubernetes.io/partners/).
|
||||
Options include:
|
||||
-->
|
||||
在自行构造 Kubernetes 生产环境之前，请考虑将这一任务的部分或者全部交给
|
||||
[云方案承包服务](/zh/docs/setup/production-environment/turnkey-solutions)
|
||||
提供商或者其他 [Kubernetes 合作伙伴](https://kubernetes.io/partners/)。
|
||||
选项有：
|
||||
|
||||
<!--
|
||||
- *Serverless*: Just run workloads on third-party equipment without managing
|
||||
a cluster at all. You will be charged for things like CPU usage, memory, and
|
||||
disk requests.
|
||||
- *Managed control plane*: Let the provider manage the scale and availability
|
||||
of the cluster's control plane, as well as handle patches and upgrades.
|
||||
- *Managed worker nodes*: Configure pools of nodes to meet your needs,
|
||||
then the provider makes sure those nodes are available and ready to implement
|
||||
upgrades when needed.
|
||||
- *Integration*: There are providers that integrate Kubernetes with other
|
||||
services you may need, such as storage, container registries, authentication
|
||||
methods, and development tools.
|
||||
-->
|
||||
- *无服务*：仅是在第三方设备上运行负载，完全不必管理集群本身。你需要为
|
||||
CPU 用量、内存和磁盘请求等付费。
|
||||
- *托管控制面*：让供应商决定集群控制面的规模和可用性，并负责打补丁和升级等操作。
|
||||
- *托管工作节点*：配置一个节点池来满足你的需要，由供应商来确保节点始终可用，
|
||||
并在需要的时候完成升级。
|
||||
- *集成*：有一些供应商能够将 Kubernetes 与一些你可能需要的其他服务集成，
|
||||
这类服务包括存储、容器镜像仓库、身份认证方法以及开发工具等。
|
||||
|
||||
<!--
|
||||
Whether you build a production Kubernetes cluster yourself or work with
|
||||
partners, review the following sections to evaluate your needs as they relate
|
||||
to your cluster’s *control plane*, *worker nodes*, *user access*, and
|
||||
*workload resources*.
|
||||
-->
|
||||
无论你是自行构造一个生产用 Kubernetes 集群还是与合作伙伴一起协作，请审阅
|
||||
下面章节以评估你的需求，因为这关系到你的集群的 *控制面*、*工作节点*、
|
||||
*用户访问* 以及 *负载资源*。
|
||||
|
||||
<!--
|
||||
## Production cluster setup
|
||||
|
||||
In a production-quality Kubernetes cluster, the control plane manages the
|
||||
cluster from services that can be spread across multiple computers
|
||||
in different ways. Each worker node, however, represents a single entity that
|
||||
is configured to run Kubernetes pods.
|
||||
-->
|
||||
## 生产用集群安装 {#production-cluster-setup}
|
||||
|
||||
在生产质量的 Kubernetes 集群中，控制面用不同的方式来管理集群和可以
|
||||
分布到多个计算机上的服务。每个工作节点则代表的是一个可配置来运行
|
||||
Kubernetes Pods 的实体。
|
||||
|
||||
<!--
|
||||
### Production control plane
|
||||
|
||||
The simplest Kubernetes cluster has the entire control plane and worker node
|
||||
services running on the same machine. You can grow that environment by adding
|
||||
worker nodes, as reflected in the diagram illustrated in
|
||||
[Kubernetes Components](/docs/concepts/overview/components/).
|
||||
If the cluster is meant to be available for a short period of time, or can be
|
||||
discarded if something goes seriously wrong, this might meet your needs.
|
||||
-->
|
||||
### 生产用控制面 {#production-control-plane}
|
||||
|
||||
最简单的 Kubernetes 集群中，整个控制面和工作节点服务都运行在同一台机器上。
|
||||
你可以通过添加工作节点来提升环境能力，正如
|
||||
[Kubernetes 组件](/zh/docs/concepts/overview/components/)示意图所示。
|
||||
如果只需要集群在很短的一段时间内可用，或者可以在某些事物出现严重问题时直接丢弃，
|
||||
这种配置可能符合你的需要。
|
||||
|
||||
<!--
|
||||
If you need a more permanent, highly available cluster, however, you should
|
||||
consider ways of extending the control plane. By design, one-machine control
|
||||
plane services running on a single machine are not highly available.
|
||||
If keeping the cluster up and running
|
||||
and ensuring that it can be repaired if something goes wrong is important,
|
||||
consider these steps:
|
||||
-->
|
||||
如果你需要一个更为持久的、高可用的集群，那么你就需要考虑扩展控制面的方式。
|
||||
根据设计，运行在一台机器上的单机控制面服务不是高可用的。
|
||||
如果保持集群处于运行状态并且需要确保在出现问题时能够被修复这点很重要，
|
||||
可以考虑以下步骤：
|
||||
|
||||
<!--
|
||||
- *Choose deployment tools*: You can deploy a control plane using tools such
|
||||
as kubeadm, kops, and kubespray. See
|
||||
[Installing Kubernetes with deployment tools](/docs/setup/production-environment/tools/)
|
||||
to learn tips for production-quality deployments using each of those deployment
|
||||
methods. Different [Container Runtimes](/docs/setup/production-environment/container-runtimes/)
|
||||
are available to use with your deployments.
|
||||
-->
|
||||
- *选择部署工具*：你可以使用类似 kubeadm、kops 和 kubespray 这类工具来部署控制面。
|
||||
参阅[使用部署工具安装 Kubernetes](/zh/docs/setup/production-environment/tools/)
|
||||
以了解使用这类部署方法来完成生产就绪部署的技巧。
|
||||
存在不同的[容器运行时](/zh/docs/setup/production-environment/container-runtimes/)
|
||||
可供你的部署采用。
|
||||
<!--
|
||||
- *Manage certificates*: Secure communications between control plane services
|
||||
are implemented using certificates. Certificates are automatically generated
|
||||
during deployment or you can generate them using your own certificate authority.
|
||||
See [PKI certificates and requirements](/docs/setup/best-practices/certificates/) for details.
|
||||
-->
|
||||
- *管理证书*：控制面服务之间的安全通信是通过证书来完成的。证书是在部署期间
|
||||
自动生成的，或者你也可以使用你自己的证书机构来生成它们。
|
||||
参阅 [PKI 证书和需求](/zh/docs/setup/best-practices/certificates/)了解细节。
|
||||
<!--
|
||||
- *Configure load balancer for apiserver*: Configure a load balancer
|
||||
to distribute external API requests to the apiserver service instances running on different nodes. See
|
||||
[Create an External Load Balancer](/docs/tasks/access-application-cluster/create-external-load-balancer/)
|
||||
for details.
|
||||
-->
|
||||
- *为 API 服务器配置负载均衡*：配置负载均衡器来将外部的 API 请求散布给运行在
|
||||
不同节点上的 API 服务实例。参阅
|
||||
[创建外部负载均衡器](/zh/docs/access-application-cluster/create-external-load-balancer/)
|
||||
了解细节。
|
||||
<!--
|
||||
- *Separate and backup etcd service*: The etcd services can either run on the
|
||||
same machines as other control plane services or run on separate machines, for
|
||||
extra security and availability. Because etcd stores cluster configuration data,
|
||||
backing up the etcd database should be done regularly to ensure that you can
|
||||
repair that database if needed.
|
||||
See the [etcd FAQ](https://etcd.io/docs/v3.4/faq/) for details on configuring and using etcd.
|
||||
See [Operating etcd clusters for Kubernetes](/docs/tasks/administer-cluster/configure-upgrade-etcd/)
|
||||
and [Set up a High Availability etcd cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)
|
||||
for details.
|
||||
-->
|
||||
- *分离并备份 etcd 服务*：etcd 服务可以运行于其他控制面服务所在的机器上，
|
||||
也可以运行在不同的机器上以获得更好的安全性和可用性。
|
||||
因为 etcd 存储着集群的配置数据，应该经常性地对 etcd 数据库进行备份，
|
||||
以确保在需要的时候你可以修复该数据库。与配置和使用 etcd 相关的细节可参阅
|
||||
[etcd FAQ](/https://etcd.io/docs/v3.4/faq/)。
|
||||
更多的细节可参阅[为 Kubernetes 运维 etcd 集群](/zh/docs/tasks/administer-cluster/configure-upgrade-etcd/)
|
||||
和[使用 kubeadm 配置高可用的 etcd 集群](/zh/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)。
|
||||
<!--
|
||||
- *Create multiple control plane systems*: For high availability, the
|
||||
control plane should not be limited to a single machine. If the control plane
|
||||
services are run by an init service (such as systemd), each service should run on at
|
||||
least three machines. However, running control plane services as pods in
|
||||
Kubernetes ensures that the replicated number of services that you request
|
||||
will always be available.
|
||||
The scheduler should be fault tolerant,
|
||||
but not highly available. Some deployment tools set up [Raft](https://raft.github.io/)
|
||||
consensus algorithm to do leader election of Kubernetes services. If the
|
||||
primary goes away, another service elects itself and take over.
|
||||
-->
|
||||
- *创建多控制面系统*：为了实现高可用性，控制面不应被限制在一台机器上。
|
||||
如果控制面服务是使用某 init 服务（例如 systemd）来运行的，每个服务应该
|
||||
至少运行在三台机器上。不过，将控制面作为服务运行在 Kubernetes Pods
|
||||
中可以确保你所请求的个数的服务始终保持可用。
|
||||
调度器应该是可容错的，但不是高可用的。
|
||||
某些部署工具会安装 [Raft](https://raft.github.io/) 票选算法来对 Kubernetes
|
||||
服务执行领导者选举。如果主节点消失，另一个服务会被选中并接手相应服务。
|
||||
<!--
|
||||
- *Span multiple zones*: If keeping your cluster available at all times is
|
||||
critical, consider creating a cluster that runs across multiple data centers,
|
||||
referred to as zones in cloud environments. Groups of zones are referred to as regions.
|
||||
By spreading a cluster across
|
||||
multiple zones in the same region, it can improve the chances that your
|
||||
cluster will continue to function even if one zone becomes unavailable.
|
||||
See [Running in multiple zones](/docs/setup/best-practices/multiple-zones/) for details.
|
||||
-->
|
||||
- *跨多个可用区*：如果保持你的集群一直可用这点非常重要，可以考虑创建一个跨
|
||||
多个数据中心的集群；在云环境中，这些数据中心被视为可用区。
|
||||
若干个可用区在一起可构成地理区域。
|
||||
通过将集群分散到同一区域中的多个可用区内，即使某个可用区不可用，整个集群
|
||||
能够继续工作的机会也大大增加。
|
||||
更多的细节可参阅[跨多个可用区运行](/zh/docs/setup/best-practices/multiple-zones/)。
|
||||
<!--
|
||||
- *Manage on-going features*: If you plan to keep your cluster over time,
|
||||
there are tasks you need to do to maintain its health and security. For example,
|
||||
if you installed with kubeadm, there are instructions to help you with
|
||||
[Certificate Management](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/)
|
||||
and [Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/).
|
||||
See [Administer a Cluster](/docs/tasks/administer-cluster/)
|
||||
for a longer list of Kubernetes administrative tasks.
|
||||
-->
|
||||
- *管理演进中的特性*：如果你计划长时间保留你的集群，就需要执行一些维护其
|
||||
健康和安全的任务。例如，如果你采用 kubeadm 安装的集群，则有一些可以帮助你完成
|
||||
[证书管理](/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/)
|
||||
和[升级 kubeadm 集群](/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade)
|
||||
的指令。
|
||||
参见[管理集群](/zh/docs/tasks/administer-cluster)了解一个 Kubernetes
|
||||
管理任务的较长列表。
|
||||
|
||||
<!--
|
||||
To learn about available options when you run control plane services, see
|
||||
[kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/),
|
||||
[kube-controller-manager](/docs/reference/command-line-tools-reference/kube-controller-manager/),
|
||||
and [kube-scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/)
|
||||
component pages. For highly available control plane examples, see
|
||||
[Options for Highly Available topology](/docs/setup/production-environment/tools/kubeadm/ha-topology/),
|
||||
[Creating Highly Available clusters with kubeadm](/docs/setup/production-environment/tools/kubeadm/high-availability/),
|
||||
and [Operating etcd clusters for Kubernetes](/docs/tasks/administer-cluster/configure-upgrade-etcd/).
|
||||
See [Backing up an etcd cluster](/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster)
|
||||
for information on making an etcd backup plan.
|
||||
-->
|
||||
要了解运行控制面服务时可使用的选项，可参阅
|
||||
[kube-apiserver](/zh/docs/reference/command-line-tools-reference/kube-apiserver/)、
|
||||
[kube-controller-manager](/zh/docs/reference/command-line-tools-reference/kube-controller-manager/) 和
|
||||
[kube-scheduler](/zh/docs/reference/command-line-tools-reference/kube-scheduler/)
|
||||
组件参考页面。
|
||||
如要了解高可用控制面的例子，可参阅
|
||||
[高可用拓扑结构选项](/zh/docs/setup/production-environment/tools/kubeadm/ha-topology/)、
|
||||
[使用 kubeadm 创建高可用集群](/zh/docs/setup/production-environment/tools/kubeadm/high-availability/) 以及[为 Kubernetes 运维 etcd 集群](/zh/docs/tasks/administer-cluster/configure-upgrade-etcd/)。
|
||||
关于制定 etcd 备份计划，可参阅
|
||||
[对 etcd 集群执行备份](/zh/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster)。
|
||||
|
||||
<!--
|
||||
### Production worker nodes
|
||||
|
||||
Production-quality workloads need to be resilient and anything they rely
|
||||
on needs to be resilient (such as CoreDNS). Whether you manage your own
|
||||
control plane or have a cloud provider do it for you, you still need to
|
||||
consider how you want to manage your worker nodes (also referred to
|
||||
simply as *nodes*).
|
||||
-->
|
||||
### 生产用工作节点
|
||||
|
||||
生产质量的工作负载需要是弹性的；它们所依赖的其他组件（例如 CoreDNS）也需要是弹性的。
|
||||
无论你是自行管理控制面还是让云供应商来管理，你都需要考虑如何管理工作节点
|
||||
（有时也简称为*节点*）。
|
||||
|
||||
<!--
|
||||
- *Configure nodes*: Nodes can be physical or virtual machines. If you want to
|
||||
create and manage your own nodes, you can install a supported operating system,
|
||||
then add and run the appropriate
|
||||
[Node services](/docs/concepts/overview/components/#node-components). Consider:
|
||||
-->
|
||||
- *配置节点*：节点可以是物理机或者虚拟机。如果你希望自行创建和管理节点，
|
||||
你可以安装一个受支持的操作系统，之后添加并运行合适的
|
||||
[节点服务](/zh/docs/concepts/overview/components/#node-components)。
|
||||
考虑：
|
||||
<!--
|
||||
- The demands of your workloads when you set up nodes by having appropriate memory, CPU, and disk speed and storage capacity available.
|
||||
- Whether generic computer systems will do or you have workloads that need GPU processors, Windows nodes, or VM isolation.
|
||||
-->
|
||||
- 在安装节点时要通过配置适当的内存、CPU 和磁盘速度、存储容量来满足
|
||||
你的负载的需求。
|
||||
- 是否通用的计算机系统即足够，还是你有负载需要使用 GPU 处理器、Windows 节点
|
||||
或者 VM 隔离。
|
||||
<!--
|
||||
- *Validate nodes*: See [Valid node setup](/docs/setup/best-practices/node-conformance/)
|
||||
for information on how to ensure that a node meets the requirements to join
|
||||
a Kubernetes cluster.
|
||||
-->
|
||||
- *验证节点*：参阅[验证节点配置](/zh/docs/setup/best-practices/node-conformance/)
|
||||
以了解如何确保节点满足加入到 Kubernetes 集群的需求。
|
||||
<!--
|
||||
- *Add nodes to the cluster*: If you are managing your own cluster you can
|
||||
add nodes by setting up your own machines and either adding them manually or
|
||||
having them register themselves to the cluster’s apiserver. See the
|
||||
[Nodes](/docs/concepts/architecture/nodes/) section for information on how to set up Kubernetes to add nodes in these ways.
|
||||
-->
|
||||
- *添加节点到集群中*：如果你自行管理你的集群，你可以通过安装配置你的机器，
|
||||
之后或者手动加入集群，或者让它们自动注册到集群的 API 服务器。参阅
|
||||
[节点](/zh/docs/concepts/architecture/nodes/)节，了解如何配置 Kubernetes
|
||||
以便以这些方式来添加节点。
|
||||
<!--
|
||||
- *Add Windows nodes to the cluster*: Kubernetes offers support for Windows
|
||||
worker nodes, allowing you to run workloads implemented in Windows containers. See
|
||||
[Windows in Kubernetes](/docs/setup/production-environment/windows/) for details.
|
||||
-->
|
||||
- *向集群中添加 Windows 节点*：Kubernetes 提供对 Windows 工作节点的支持；
|
||||
这使得你可以运行实现于 Windows 容器内的工作负载。参阅
|
||||
[Kubernetes 中的 Windows](/zh/docs/setup/production-environment/windows/)
|
||||
了解进一步的详细信息。
|
||||
<!--
|
||||
- *Scale nodes*: Have a plan for expanding the capacity your cluster will
|
||||
eventually need. See [Considerations for large clusters](/docs/setup/best-practices/cluster-large/)
|
||||
to help determine how many nodes you need, based on the number of pods and
|
||||
containers you need to run. If you are managing nodes yourself, this can mean
|
||||
purchasing and installing your own physical equipment.
|
||||
-->
|
||||
- *扩缩节点*：制定一个扩充集群容量的规划，你的集群最终会需要这一能力。
|
||||
参阅[大规模集群考察事项](/zh/docs/setup/best-practices/cluster-large/)
|
||||
以确定你所需要的节点数；这一规模是基于你要运行的 Pod 和容器个数来确定的。
|
||||
如果你自行管理集群节点，这可能意味着要购买和安装你自己的物理设备。
|
||||
<!--
|
||||
- *Autoscale nodes*: Most cloud providers support
|
||||
[Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#readme)
|
||||
to replace unhealthy nodes or grow and shrink the number of nodes as demand requires. See the
|
||||
[Frequently Asked Questions](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md)
|
||||
for how the autoscaler works and
|
||||
[Deployment](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#deployment)
|
||||
for how it is implemented by different cloud providers. For on-premises, there
|
||||
are some virtualization platforms that can be scripted to spin up new nodes
|
||||
based on demand.
|
||||
-->
|
||||
- *节点自动扩缩容*：大多数云供应商支持
|
||||
[集群自动扩缩器（Cluster Autoscaler）](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#readme)
|
||||
以便替换不健康的节点、根据需求来增加或缩减节点个数。参阅
|
||||
[常见问题](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md)
|
||||
了解自动扩缩器的工作方式，并参阅
|
||||
[Deployment](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#deployment)
|
||||
了解不同云供应商是如何实现集群自动扩缩器的。
|
||||
对于本地集群，有一些虚拟化平台可以通过脚本来控制按需启动新节点。
|
||||
<!--
|
||||
- *Set up node health checks*: For important workloads, you want to make sure
|
||||
that the nodes and pods running on those nodes are healthy. Using the
|
||||
[Node Problem Detector](/docs/tasks/debug-application-cluster/monitor-node-health/)
|
||||
daemon, you can ensure your nodes are healthy.
|
||||
-->
|
||||
- *安装节点健康检查*：对于重要的工作负载，你会希望确保节点以及在节点上
|
||||
运行的 Pod 处于健康状态。通过使用
|
||||
[Node Problem Detector](/zh/docs/tasks/debug-application-cluster/monitor-node-health/)，
|
||||
你可以确保你的节点是健康的。
|
||||
|
||||
<!--
|
||||
## Production user management
|
||||
|
||||
In production, you may be moving from a model where you or a small group of
|
||||
people are accessing the cluster to where there may potentially be dozens or
|
||||
hundreds of people. In a learning environment or platform prototype, you might have a single
|
||||
administrative account for everything you do. In production, you will want
|
||||
more accounts with different levels of access to different namespaces.
|
||||
-->
|
||||
### 生产级用户环境
|
||||
|
||||
在生产环境中，情况可能不再是你或者一小组人在访问集群，而是几十
|
||||
上百人需要访问集群。在学习环境或者平台原型环境中，你可能具有一个
|
||||
可以执行任何操作的管理账号。在生产环境中，你可需要对不同名字空间
|
||||
具有不同访问权限级别的很多账号。
|
||||
|
||||
<!--
|
||||
Taking on a production-quality cluster means deciding how you
|
||||
want to selectively allow access by other users. In particular, you need to
|
||||
select strategies for validating the identities of those who try to access your
|
||||
cluster (authentication) and deciding if they have permissions to do what they
|
||||
are asking (authorization):
|
||||
-->
|
||||
建立一个生产级别的集群意味着你需要决定如何有选择地允许其他用户访问集群。
|
||||
具体而言，你需要选择验证尝试访问集群的人的身份标识（身份认证），并确定
|
||||
他们是否被许可执行他们所请求的操作（鉴权）：
|
||||
|
||||
<!--
|
||||
- *Authentication*: The apiserver can authenticate users using client
|
||||
certificates, bearer tokens, an authenticating proxy, or HTTP basic auth.
|
||||
You can choose which authentication methods you want to use.
|
||||
Using plugins, the apiserver can leverage your organization’s existing
|
||||
authentication methods, such as LDAP or Kerberos. See
|
||||
[Authentication](/docs/reference/access-authn-authz/authentication/)
|
||||
for a description of these different methods of authenticating Kubernetes users.
|
||||
-->
|
||||
- *认证（Authentication）*：API 服务器可以使用客户端证书、持有者令牌、身份
|
||||
认证代理或者 HTTP 基本认证机制来完成身份认证操作。
|
||||
你可以选择你要使用的认证方法。通过使用插件，API 服务器可以充分利用你所在
|
||||
组织的现有身份认证方法，例如 LDAP 或者 Kerberos。
|
||||
关于认证 Kubernetes 用户身份的不同方法的描述，可参阅
|
||||
[身份认证](/zh/docs/reference/access-authn-authz/authentication/)。
|
||||
<!--
|
||||
- *Authorization*: When you set out to authorize your regular users, you will probably choose between RBAC and ABAC authorization. See [Authorization Overview](/docs/reference/access-authn-authz/authorization/) to review different modes for authorizing user accounts (as well as service account access to your cluster):
|
||||
-->
|
||||
- *鉴权（Authorization）*：当你准备为一般用户执行权限判定时，你可能会需要
|
||||
在 RBAC 和 ABAC 鉴权机制之间做出选择。参阅
|
||||
[鉴权概述](/zh/docs/reference/access-authn-authz/authorization/)，了解
|
||||
对用户账户（以及访问你的集群的服务账户）执行鉴权的不同模式。
|
||||
<!--
|
||||
- *Role-based access control* ([RBAC](/docs/reference/access-authn-authz/rbac/)): Lets you assign access to your cluster by allowing specific sets of permissions to authenticated users. Permissions can be assigned for a specific namespace (Role) or across the entire cluster (ClusterRole). Then using RoleBindings and ClusterRoleBindings, those permissions can be attached to particular users.
|
||||
-->
|
||||
- *基于角色的访问控制*（[RBAC](/zh/docs/reference/access-authn-authz/rbac/)）：
|
||||
让你通过为通过身份认证的用户授权特定的许可集合来控制集群访问。
|
||||
访问许可可以针对某特定名字空间（Role）或者针对整个集群（CLusterRole）。
|
||||
通过使用 RoleBinding 和 ClusterRoleBinding 对象，这些访问许可可以被
|
||||
关联到特定的用户身上。
|
||||
<!--
|
||||
- *Attribute-based access control* ([ABAC](/docs/reference/access-authn-authz/abac/)): Lets you create policies based on resource attributes in the cluster and will allow or deny access based on those attributes. Each line of a policy file identifies versioning properties (apiVersion and kind) and a map of spec properties to match the subject (user or group), resource property, non-resource property (/version or /apis), and readonly. See [Examples](/docs/reference/access-authn-authz/abac/#examples) for details.
|
||||
-->
|
||||
- *基于属性的访问控制*（[ABAC](/zh/docs/reference/access-authn-authz/abac/)）：
|
||||
让你能够基于集群中资源的属性来创建访问控制策略，基于对应的属性来决定
|
||||
允许还是拒绝访问。策略文件的每一行都给出版本属性（apiVersion 和 kind）
|
||||
以及一个规约属性的映射，用来匹配主体（用户或组）、资源属性、非资源属性
|
||||
（/version 或 /apis）和只读属性。
|
||||
参阅[示例](/zh/docs/reference/access-authn-authz/abac/#examples)以了解细节。
|
||||
|
||||
<!--
|
||||
As someone setting up authentication and authorization on your production Kubernetes cluster, here are some things to consider:
|
||||
-->
|
||||
作为在你的生产用 Kubernetes 集群中安装身份认证和鉴权机制的负责人，
|
||||
要考虑的事情如下：
|
||||
|
||||
<!--
|
||||
- *Set the authorization mode*: When the Kubernetes API server
|
||||
([kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/))
|
||||
starts, the supported authentication modes must be set using the *--authorization-mode*
|
||||
flag. For example, that flag in the *kube-adminserver.yaml* file (in */etc/kubernetes/manifests*)
|
||||
could be set to Node,RBAC. This would allow Node and RBAC authorization for authenticated requests.
|
||||
-->
|
||||
- *设置鉴权模式*：当 Kubernetes API 服务器
|
||||
（[kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/)）
|
||||
启动时，所支持的鉴权模式必须使用 `--authorization-mode` 标志配置。
|
||||
例如，`kube-apiserver.yaml`（位于 `/etc/kubernetes/manifests` 下）中对应的
|
||||
标志可以设置为 `Node,RBAC`。这样就会针对已完成身份认证的请求执行 Node 和 RBAC
|
||||
鉴权。
|
||||
<!--
|
||||
- *Create user certificates and role bindings (RBAC)*: If you are using RBAC
|
||||
authorization, users can create a CertificateSigningRequest (CSR) that can be
|
||||
signed by the cluster CA. Then you can bind Roles and ClusterRoles to each user.
|
||||
See [Certificate Signing Requests](/docs/reference/access-authn-authz/certificate-signing-requests/)
|
||||
for details.
|
||||
-->
|
||||
- *创建用户证书和角色绑定（RBAC）*：如果你在使用 RBAC 鉴权，用户可以创建
|
||||
由集群 CA 签名的 CertificateSigningRequest（CSR）。接下来你就可以将 Role
|
||||
和 ClusterRole 绑定到每个用户身上。
|
||||
参阅[证书签名请求](/zh/docs/reference/access-authn-authz/certificate-signing-requests/)
|
||||
了解细节。
|
||||
<!--
|
||||
- *Create policies that combine attributes (ABAC)*: If you are using ABAC
|
||||
authorization, you can assign combinations of attributes to form policies to
|
||||
authorize selected users or groups to access particular resources (such as a
|
||||
pod), namespace, or apiGroup. For more information, see
|
||||
[Examples](/docs/reference/access-authn-authz/abac/#examples).
|
||||
-->
|
||||
- *创建组合属性的策略（ABAC）*：如果你在使用 ABAC 鉴权，你可以设置属性组合
|
||||
以构造策略对所选用户或用户组执行鉴权，判定他们是否可访问特定的资源
|
||||
（例如 Pod）、名字空间或者 apiGroup。进一步的详细信息可参阅
|
||||
[示例](/zh/docs/reference/access-authn-authz/abac/#examples)。
|
||||
<!--
|
||||
- *Consider Admission Controllers*: Additional forms of authorization for
|
||||
requests that can come in through the API server include
|
||||
[Webhook Token Authentication](/docs/reference/access-authn-authz/authentication/#webhook-token-authentication).
|
||||
Webhooks and other special authorization types need to be enabled by adding
|
||||
[Admission Controllers](/docs/reference/access-authn-authz/admission-controllers/)
|
||||
to the API server.
|
||||
-->
|
||||
- *考虑准入控制器*：针对指向 API 服务器的请求的其他鉴权形式还包括
|
||||
[Webhook 令牌认证](/zh/docs/reference/access-authn-authz/authentication/#webhook-token-authentication)。
|
||||
Webhook 和其他特殊的鉴权类型需要通过向 API 服务器添加
|
||||
[准入控制器](/zh/docs/reference/access-authn-authz/admission-controllers/)
|
||||
来启用。
|
||||
|
||||
<!--
|
||||
## Set limits on workload resources
|
||||
|
||||
Demands from production workloads can cause pressure both inside and outside
|
||||
of the Kubernetes control plane. Consider these items when setting up for the
|
||||
needs of your cluster's workloads:
|
||||
-->
|
||||
## 为负载资源设置约束 {#set-limits-on-workload-resources}
|
||||
|
||||
生产环境负载的需求可能对 Kubernetes 的控制面内外造成压力。
|
||||
在针对你的集群的负载执行配置时，要考虑以下条目：
|
||||
|
||||
<!--
|
||||
- *Set namespace limits*: Set per-namespace quotas on things like memory and CPU. See
|
||||
[Manage Memory, CPU, and API Resources](/docs/tasks/administer-cluster/manage-resources/)
|
||||
for details. You can also set
|
||||
[Hierarchical Namespaces](/blog/2020/08/14/introducing-hierarchical-namespaces/)
|
||||
for inheriting limits.
|
||||
-->
|
||||
- *设置名字空间限制*：为每个名字空间的内存和 CPU 设置配额。
|
||||
参阅[管理内存、CPU 和 API 资源](/zh/docs/tasks/administer-cluster/manage-resources/)
|
||||
以了解细节。你也可以设置
|
||||
[层次化名字空间](/blog/2020/08/14/introducing-hierarchical-namespaces/)
|
||||
来继承这类约束。
|
||||
<!--
|
||||
- *Prepare for DNS demand*: If you expect workloads to massively scale up,
|
||||
your DNS service must be ready to scale up as well. See
|
||||
[Autoscale the DNS service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).
|
||||
-->
|
||||
- *为 DNS 请求做准备*：如果你希望工作负载能够完成大规模扩展，你的 DNS 服务
|
||||
也必须能够扩大规模。参阅
|
||||
[自动扩缩集群中 DNS 服务](/zh/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)。
|
||||
<!--
|
||||
- *Create additional service accounts*: User accounts determine what users can
|
||||
do on a cluster, while a service account defines pod access within a particular
|
||||
namespace. By default, a pod takes on the default service account from its namespace.
|
||||
See [Managing Service Accounts](/docs/reference/access-authn-authz/service-accounts-admin/)
|
||||
for information on creating a new service account. For example, you might want to:
|
||||
-->
|
||||
- *创建额外的服务账户*：用户账户决定用户可以在集群上执行的操作，服务账号则定义的
|
||||
是在特定名字空间中 Pod 的访问权限。
|
||||
默认情况下，Pod 使用所在名字空间中的 default 服务账号。
|
||||
参阅[管理服务账号](/zh/docs/reference/access-authn-authz/service-accounts-admin/)
|
||||
以了解如何创建新的服务账号。例如，你可能需要：
|
||||
<!--
|
||||
- Add secrets that a pod could use to pull images from a particular container registry. See [Configure Service Accounts for Pods](/docs/tasks/configure-pod-container/configure-service-account/) for an example.
|
||||
- Assign RBAC permissions to a service account. See [ServiceAccount permissions](/docs/reference/access-authn-authz/rbac/#service-account-permissions) for details.
|
||||
-->
|
||||
- 为 Pod 添加 Secret，以便 Pod 能够从某特定的容器镜像仓库拉取镜像。
|
||||
参阅[为 Pod 配置服务账号](/zh/docs/tasks/configure-pod-container/configure-service-account/)
|
||||
以获得示例。
|
||||
- 为服务账号设置 RBAC 访问许可。参阅
|
||||
[服务账号访问许可](/zh/docs/reference/access-authn-authz/rbac/#service-account-permissions)
|
||||
了解细节。
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
<!--
|
||||
- Decide if you want to build your own production Kubernetes or obtain one from
|
||||
available [Turnkey Cloud Solutions](/docs/setup/production-environment/turnkey-solutions/)
|
||||
or [Kubernetes Partners](https://kubernetes.io/partners/).
|
||||
- If you choose to build your own cluster, plan how you want to
|
||||
handle [certificates](/docs/setup/best-practices/certificates/)
|
||||
and set up high availability for features such as
|
||||
[etcd](/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)
|
||||
and the
|
||||
[API server](/docs/setup/production-environment/tools/kubeadm/ha-topology/).
|
||||
-->
|
||||
- 决定你是想自行构造自己的生产用 Kubernetes 还是从某可用的
|
||||
[云服务外包厂商](/zh/docs/setup/production-environment/turnkey-solutions/)
|
||||
或 [Kubernetes 合作伙伴](https://kubernetes.io/partners/)获得集群。
|
||||
- 如果你决定自行构造集群，则需要规划如何处理
|
||||
[证书](/zh/docs/setup/best-practices/certificates/)
|
||||
并为类似
|
||||
[etcd](/zh/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)
|
||||
和
|
||||
[API 服务器](/zh/docs/setup/production-environment/tools/kubeadm/ha-topology/)
|
||||
这些功能组件配置高可用能力。
|
||||
<!--
|
||||
- Choose from [kubeadm](/docs/setup/production-environment/tools/kubeadm/), [kops](/docs/setup/production-environment/tools/kops/) or [Kubespray](/docs/setup/production-environment/tools/kubespray/)
|
||||
deployment methods.
|
||||
-->
|
||||
- 选择使用 [kubeadm](/zh/docs/setup/production-environment/tools/kubeadm/)、
|
||||
[kops](/zh/docs/setup/production-environment/tools/kops/) 或
|
||||
[Kubespray](/zh/docs/setup/production-environment/tools/kubespray/)
|
||||
作为部署方法。
|
||||
<!--
|
||||
- Configure user management by determining your
|
||||
[Authentication](/docs/reference/access-authn-authz/authentication/) and
|
||||
[Authorization](/docs/reference/access-authn-authz/authorization/) methods.
|
||||
-->
|
||||
- 通过决定[身份认证](/zh/docs/reference/access-authn-authz/authentication/)和
|
||||
[鉴权](/zh/docs/reference/access-authn-authz/authorization/)方法来配置用户管理。
|
||||
<!--
|
||||
- Prepare for application workloads by setting up
|
||||
[resource limits](/docs/tasks/administer-cluster/manage-resources/),
|
||||
[DNS autoscaling](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)
|
||||
and [service accounts](/docs/reference/access-authn-authz/service-accounts-admin/).
|
||||
-->
|
||||
- 通过配置[资源限制](/zh/docs/tasks/administer-cluster/manage-resources/)、
|
||||
[DNS 自动扩缩](/zh/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)
|
||||
和[服务账号](/zh/docs/reference/access-authn-authz/service-accounts-admin/)
|
||||
来为应用负载作准备。
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue