Micro-service cluster deployment method and device, computer equipment and storage medium

Abstract

The invention discloses a micro-service cluster deployment method and device, computer equipment and a storage medium. The method comprises the steps: receiving a micro-service cluster deployment instruction, and obtaining a micro-service cluster deployment file; storing the target environment configuration package into a local warehouse, making the target environment configuration package into aDocker mirror image file through a Docker tool, associating the Docker mirror image file with the name of the environment configuration package, and uploading the Docker mirror image file to a Dockerregistration machine; querying whether an environment cluster name consistent with the target environment cluster name exists in a Kubernetes cluster container or not through a Helm tool; creating a first micro-service cluster consistent with the target environment cluster name; installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker mirror image file to all first target nodes; and setting up the environment configuration of the first micro-service cluster through a Helm tool. According to the method, the cluster under the Kubernetes cluster container is automatically configured, manual configuration is reduced, and the building efficiency is improved.

Description

technical field [0001] The present invention relates to the field of microservice architecture, in particular to a microservice cluster deployment method, device, computer equipment and storage medium. Background technique [0002] In the existing technology, the Kubernetes cluster container scheduling and orchestration technology divides the resources managed by a single operating system into isolated groups. The Kubernetes cluster container scheduling and orchestration technology can be understood as a sandbox, and each container runs an application. The containers are isolated from each other, but a communication mechanism can be established between the containers. However, manual configuration is required to build a Kubernetes cluster, which is labor-intensive and inefficient in production operation and maintenance. Moreover, as the frequency of iterative upgrades increases, the labor cost will increase, especially in the case of exceptions that require return When roll...

AI Technical Summary

Problems solved by technology

However, manual configuration is required to build a Kubernetes cluster, which is labor-intensive and inefficient in production operation and maintenance. Moreover, as the frequency of iterative upgrades increases, the labor cost will increase, especially in the case of exceptions that require return When rolling the historical version of the business application on the Kubernetes cluster, since Kubernetes does not natively support the rollback function

Helm's rollback function requires command line operations to specifically query the historical version, and cannot distinguish the environment where the application is located, which consumes higher labor costs and lower operation and maintenance efficiency

Images