[英]How does kubernetes maintain the deployment yaml internally. Where will be it stored after the first deployment
Once you deploy a pod, kubernetes monitors the pod health and if something goes wrong, new pod is created . 部署Pod后,kubernetes会监视Pod的运行状况,如果出现问题,则会创建新Pod。 How is this working internally. 这在内部如何运作。 After deployment, where is kubernetes storing the deployment yaml. 部署后,kubernetes在哪里存储部署yaml。
Kubernetes uses the ETCD database as data store. Kubernetes使用ETCD数据库作为数据存储。 The flow is like this. 流程是这样的。 Kubectl command connect to API server and sends the yaml file to API server. Kubectl命令连接到API服务器,并将yaml文件发送到API服务器。 API parses and store the information in ETCD database. API解析信息并将其存储在ETCD数据库中。 Kube controller and schedule looks at the ETCD database and starts the POD. Kube控制器和日程表查看ETCD数据库并启动POD。 Controller maintain the number of replica defined in the yaml file. 控制器维护yaml文件中定义的副本数。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.