kubernetes 的工作流程
1.用户创建Kubernetes的YAML文件来描述应用程序的期望状态。
The user creates a YAML file to describe the desired state of the application in Kubernetes.
2.用户将YAML文件提交给Kubernetes集的API服务器。
The user submits the YAML file to the API server of the Kubernetes cluster.
3. API服务器验证和接受YAML文件，并将其存储在etcd中。
The API server validates and accepts the YAML file, and stores it in etcd.
4.控制器管理器检测到新的YAML文件，并创建相应的控制器。
The controller manager detects the new YAML file and creates the corresponding controller.
5.控制器创建了pods、services和其他资源来满足YAML文件中描述的状态。
The controller creates pods, services, and other resources to meet the state described in the YAML file.
6. kubelet检测到新的pods，并向Docker引擎发送请求以创建容器。
The kubelet detects the new pods and sends requests to the Docker engine to create containers.
7. Docker引擎创建并启动容器，然后报告给kubelet。
The Docker engine creates and starts the containers, and reports back to the kubelet.
8. kubelet监视容器的状态，并将状态信息返回给API服务器。
container容器用法The kubelet monitors the status of the containers and sends the status information back to the API server.
9. API服务器更新etcd中的状态，以匹配实际状态。
The API server updates the state in etcd to match the actual status.
10.用户可以通过kubectl工具查看应用程序的状态并管理它。
The user can use the kubectl tool to view the status of the application and manage it.
11.控制器管理器通过反复循环检测应用程序状态并做出必要的更改。
The controller manager detects the application status through repeated loops and makes necessary changes.
12. kubelet持续监视容器的状态，并在需要时重新启动失败的容器。
The kubelet continuously monitors the status of the container and restarts failed containers if necessary.
13.容器中的应用程序将通过服务暴露给其他应用程序或用户。
The application in the container is exposed to other applications or users through services.
14.用户可以通过kubectl修改YAML文件来更新应用程序的期望状态。
The user can update the desired state of the application by modifying the YAML file using kubectl.
15.在部署期间，Kubernetes会自动处理故障转移以确保应用程序的高可用性。
During deployment, Kubernetes automatically handles failover to ensure high availability of the application.
16.通过声明式的YAML文件，Kubernetes使应用程序状态的管理变得简单而灵活。
With declarative YAML files, Kubernetes makes it simple and flexible to manage the state of applications.
17.控制器监控pods的健康状态，并根据需要进行自愈操作。
The controller monitors the health status of pods and performs self-healing operations as needed.
18. kubelet定期向API服务器报告节点的状态和资源使用情况。
The kubelet regularly reports the status of the node and resource usage to the API server.
19. API服务器利用存储在etcd中的状态信息来决定执行何种操作。
The API server uses the state information stored in etcd to determine what actions to take.
20.控制器管理器能够调整资源配置以满足应用程序的需求。
The controller manager can adjust resource configurations to meet the needs of the application.
21. kubelet利用CRI（容器运行时接口）与任何容器运行时进行通信。

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。