A kubernetes deployment method and system

Abstract

The present application relates to a kind of kubernetes deployment method and system, it is related to service deployment field, this method includes: obtaining tenant target service information according to tenant service demand, tenant target service information includes multiple service applications and the version information corresponding to each service application;According to tenant target service information, the configuration information corresponding to each service application is extracted from the archive warehouse, and initial overall configuration file is generated;Archive warehouse includes the archive information of multiple service applications;The configuration information of initial overall configuration file is divided into common configuration and difference configuration;Tenant deployment package is built;Tenant deployment package includes tenant target service information, common configuration and difference configuration;According to deployment package, each service application in tenant target service information is deployed into kubernetes.The present application improves deployment efficiency.

Description

Technical Field

[0001] This invention relates to the field of service deployment technology, and in particular to a Kubernetes deployment method and system. Background Technology

[0002] To provide enterprises with a better internet experience, cloud-native cluster solutions are being used to expand from single machines to clusters. In particular, in microservice architectures and multi-tenant customizable enterprise service models, how to quickly create and run services and environments for tenant enterprises has become a complex issue.

[0003] General approach: When deploying services to tenant enterprises, it's necessary to select which services and versions to deploy, record feasible methods, and then have operations personnel manually deploy them one by one. In addition to completing the service deployment configuration files, configuration files for the services on the cluster also need to be completed. For operations personnel, deploying a service for an entire enterprise is extremely complex and can also impact the archiving aspects of project management.

[0004] Pipeline-based solutions: Cloud-native solutions mention a pipeline-based deployment approach. This approach can alleviate the problem of manual deployment by operations and maintenance personnel to some extent. It allows deployment of enterprise services through a tool interface using pre-configured settings and a set of optional configurations. The problem with this approach is that when deploying each service, the pipeline lacks information describing the entire enterprise, which services were deployed, and which versions of those services. Furthermore, version archiving is not possible after modifying cluster configuration files, and the use and creation of pipelines themselves introduce additional complexity and learning costs. Summary of the Invention

[0005] The purpose of this invention is to provide a Kubernetes deployment method and system that improves deployment efficiency.

[0006] To achieve the above objectives, the present invention provides the following solution:

[0007] A Kubernetes deployment method includes:

[0008] The tenant's target service information is obtained based on the tenant's service requirements. The tenant's target service information includes multiple service applications and version information corresponding to each service application.

[0009] Based on the tenant's target service information, the configuration information corresponding to each service application is extracted from the archive repository to generate an initial overall configuration file. The archive repository includes archive information for multiple service applications. The archive information for each service application includes code image, version information, and configuration information. The configuration information includes code configuration and cluster configuration. The cluster configuration is the configuration for deploying the service application to Kubernetes.

[0010] The configuration information of the initial overall configuration file is divided into common configuration and differential configuration;

[0011] Construct a tenant deployment package; the tenant deployment package includes the tenant's target service information, the common configuration, and the differential configuration;

[0012] The service applications in the tenant target service information are deployed to Kubernetes according to the deployment package.

[0013] Optionally, the configuration information of the initial overall configuration file can be divided into common configuration and differential configuration, specifically including:

[0014] The initial overall configuration file is traversed line by line, and the configuration name is used as the key to count the number of occurrences.

[0015] Configuration names that appear once are designated as differential configurations, while configuration names that appear more than once are designated as common configurations.

[0016] Optionally, the configuration information of the initial overall configuration file can be divided into common configuration and differential configuration, specifically including:

[0017] All common configurations are stored in a common node, and each differential configuration is stored in a differential node named after the corresponding service application.

[0018] Optionally, deploying each of the service applications in the tenant target service information to Kubernetes according to the deployment package specifically includes:

[0019] For the configuration information of each service application extracted from the archive repository based on the tenant target service information: the configuration information is traversed line by line to determine whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application to obtain the complete configuration information of the current service application.

[0020] Each service application is deployed to Kubernetes based on its complete configuration information.

[0021] This invention also discloses a Kubernetes deployment system, comprising:

[0022] The tenant target service information determination module is used to obtain tenant target service information based on tenant service requirements. The tenant target service information includes multiple service applications and version information corresponding to each service application.

[0023] The initial overall configuration file generation module is used to extract the configuration information corresponding to each service application from the archive repository based on the tenant target service information, and generate the initial overall configuration file; the archive repository includes archive information of multiple service applications, and the archive information of each service application includes code image, version information and configuration information, and the configuration information includes code configuration and cluster configuration; the cluster configuration is the configuration for deploying the service application to Kubernetes;

[0024] The common configuration and differential configuration differentiation module is used to differentiate the configuration information of the initial overall configuration file into common configuration and differential configuration;

[0025] The deployment package building module is used to build tenant deployment packages; the tenant deployment package includes the tenant target service information, the common configuration, and the differential configuration;

[0026] Each service application deployment module is used to deploy each of the service applications in the tenant target service information to Kubernetes according to the deployment package.

[0027] Optionally, the common configuration and differential configuration differentiation module specifically includes:

[0028] The configuration name occurrence count module is used to iterate through the initial overall configuration file line by line and count the occurrence count of the configuration name as the key.

[0029] The common configuration and differential configuration differentiation unit is used to classify configuration names that appear once as differential configurations and configuration names that appear more than once as common configurations.

[0030] Optionally, the common configuration and differential configuration differentiation module further includes:

[0031] The storage unit is used to store all the common configurations in the common node and store each differential configuration in the differential node named after the corresponding service application.

[0032] Optionally, each service application deployment module specifically includes:

[0033] The configuration information combination unit is used to: for each service application configuration information extracted from the archive repository based on the tenant target service information, the configuration information is traversed line by line to determine whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application to obtain the complete configuration information of the current service application.

[0034] Each service application deployment unit is used to deploy each service application to Kubernetes based on the complete configuration information of each service application.

[0035] According to specific embodiments provided by the present invention, the present invention discloses the following technical effects:

[0036] This invention discloses a Kubernetes deployment method and system. It obtains tenant target service information based on tenant service requirements, extracts configuration information corresponding to each service application from an archive repository, generates an initial overall configuration file, and distinguishes between common configuration and differential configuration. Based on the tenant target service information, common configuration, and differential configuration, it deploys each service application from the tenant target service information to Kubernetes, automatically generating configuration files for each service application. Furthermore, the common configuration can cover all common configuration information at once, improving deployment efficiency. This invention enables rapid multi-service Kubernetes deployment for each tenant and is suitable for rapid multi-tenant, multi-service Kubernetes deployment. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram of a Kubernetes deployment method according to the present invention;

[0039] Figure 2 This is a schematic diagram illustrating the construction of the archive repository for this invention;

[0040] Figure 3 This is a schematic diagram illustrating the process of generating a deployment package for this invention;

[0041] Figure 4 This is a schematic diagram of the enterprise tenant deployment process of the present invention;

[0042] Figure 5 This is a schematic diagram of the initial overall configuration file generation process of this invention;

[0043] Figure 6 This is a schematic diagram of the configuration set generation process for the present invention;

[0044] Figure 7 This is a schematic diagram of the common configuration and differential configuration extraction process of this invention;

[0045] Figure 8 This is a schematic diagram illustrating the deployment process of each service application of the present invention;

[0046] Figure 9 This is a schematic diagram illustrating the complete configuration and combination process of each service application of the present invention;

[0047] Figure 10 This is a schematic diagram of a Kubernetes deployment system architecture according to the present invention. Detailed Implementation

[0048] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] The purpose of this invention is to provide a Kubernetes deployment method and system that improves deployment efficiency.

[0050] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0051] Figure 1 This is a schematic diagram of a Kubernetes deployment method according to the present invention, as shown below. Figure 1 As shown, a Kubernetes deployment method includes:

[0052] Step 101: Obtain the tenant's target service information based on the tenant's service requirements. The tenant's target service information includes multiple service applications and the version information of each service application.

[0053] Step 101 specifically includes: obtaining the tenant's target service information based on the template file and the tenant's service requirements. Specifically, an empty template file is automatically generated in the path of the automated deployment tool, and then given to the operations and maintenance personnel to fill in the service and version information.

[0054] Step 102: Based on the tenant's target service information, extract the configuration information corresponding to each service application from the archive repository to generate the initial overall configuration file; the archive repository includes archive information of multiple service applications, and the archive information of each service application includes code image, version information and configuration information. The configuration information includes code configuration and cluster configuration; the cluster configuration is the configuration for deploying the service application to Kubernetes.

[0055] The code image is specifically a binary image.

[0056] The present invention provides a Kubernetes deployment method, which is a cloud-native Kubernetes deployment method.

[0057] Figure 2 The diagram illustrates the construction of the archive repository, including the service module release process. The goal of service module release is to build the binary image of the service (service application) and the corresponding configuration information. In subsequent steps, the data produced in this step will be used for operations such as acquisition, comparison, analysis, and merging. This step is the most basic element of the entire deployment scheme.

[0058] During the development phase, R&D personnel produce code images and code configurations, while operations and maintenance personnel produce cluster configurations that match the requirements of the current version. After the project is released, these are archived in the archive repository.

[0059] The archive repository includes the output service version and corresponding configuration information. Subsequent steps require checking whether the corresponding version exists for the specific service, analyzing the obtained configuration information, extracting common and private configurations (differentiated configurations), and completing the overall configuration combination for use in subsequent processes.

[0060] Step 103: Divide the configuration information of the initial overall configuration file into common configuration and differential configuration.

[0061] The common configuration also includes the default configuration and the configuration that needs to be modified for each configuration name. The default configuration value is the corresponding configuration value in the configuration information in the archive repository. The configuration value of the configuration that needs to be modified is modified according to the actual needs. Specifically, the operation and maintenance personnel modify the configuration value of the configuration that needs to be modified according to the actual deployment environment.

[0062] The process of generating a configuration file that includes both common and differential configurations is as follows: Figure 5As shown in the diagram. In this process, based on the services and versions of the enterprise tenants filled in by the operations and maintenance personnel, the automated deployment tool reads the service and version files filled in by the operations and maintenance personnel, obtains the service and version information filled in by the enterprise tenants, and uses this as a basis to retrieve the accessibility of the corresponding services and the configuration information of the corresponding versions from the archive repository, which are then handed over to subsequent processes for analysis, extraction and merging.

[0063] By analyzing the configuration, the entire configuration set retrieved from the archive repository is traversed line by line, and the configuration key and value are written into the configuration set. The number of occurrences is then counted to extract the common and differential configurations of the service. The configuration set is generated as follows: Figure 6 As shown. The extraction of common and differential configurations is as follows. Figure 7 As shown.

[0064] The automated deployment tool, based on the configuration set generated by the above analysis and configuration steps, quickly distinguishes between common and differential configurations by the frequency of configuration names. For common configurations, the service node itself is no longer considered its own node, but is stored under a unified Global node, indicating that it is a common configuration; while differential configurations are used exclusively by the service itself, and are therefore stored under a node that begins with the service name.

[0065] Finally, the tool combines the final configuration into a single output package for the enterprise tenant. The final deployment package contains the services the enterprise tenant needs to deploy, along with their corresponding version numbers. The tool also renders the overall configuration files for the selected services, eliminating the hassle of manual configuration for each service by operations personnel. Furthermore, repeated configurations only need to be configured once to cover all used services.

[0066] This process takes into account service updates for enterprise tenants. Since there may be previously configured overall deployment packages containing most of the information, the automated deployment tool attempts to merge the values ​​of existing configuration files into the new overall configuration when generating the new configuration. This prevents operations personnel from having to manually reconfigure the configuration after regeneration.

[0067] Step 103 specifically includes:

[0068] The initial overall configuration file is traversed line by line, and the configuration name is used as the key to count the number of occurrences.

[0069] Configuration names that appear once are designated as differential configurations, while configuration names that appear more than once are designated as common configurations.

[0070] Store all common configurations in the common node, and store each differential configuration in a differential node named after the corresponding service application.

[0071] Step 104: Build the tenant deployment package; the tenant deployment package includes tenant target service information, common configuration and differential configuration.

[0072] The archive repository contains numerous services and their corresponding version information. However, the output files in the archive repository can only describe a single service and cannot represent the whole. For enterprise tenants, in a microservice architecture, an information file describing all services and versions of the enterprise tenant is needed to generate the overall deployment package. Service and version information is obtained from the archive repository, and the differences between the service version configuration files are compared, analyzed, extracted, and combined to form a comprehensive description of the services and configuration files, thus creating the deployment package. The deployment package generation process is as follows: Figure 3 As shown.

[0073] The operations and maintenance personnel use the deployment tool to initialize the template to generate the configuration template. This configuration template is generated by the automatic deployment tool because the automatic deployment tool needs to identify specific file formats and the corresponding default file content header. To reduce the complexity for operations and maintenance personnel, the automatic deployment tool generates the template, and the operations and maintenance personnel only need to focus on the content that needs to be filled in.

[0074] Then, the operations and maintenance personnel fill in the service and version information to be deployed to the enterprise tenant based on the obtained configuration template. This information specifies the services and versions that the enterprise tenant needs to deploy, and the actual service content delivered to the enterprise tenant will be based on the service and version information filled in here. After the service and version information is filled in here, subsequent steps will analyze and use this information as a basis to search for service reachability in the archive repository, as well as analyze and extract configuration files. Then, the deployment tool renders the overall configuration of the enterprise tenant that needs to be modified. After this step is completed by the tool, the generated overall configuration file describes the configuration information required for the deployment or runtime of the enterprise tenant service, including the default configuration and the configuration that needs to be modified. The operations and maintenance personnel modify the configuration file as needed to ensure the correctness of the enterprise tenant's service data and other configuration dependencies in a specific environment. After the operations and maintenance personnel modify the configuration, a complete deployment package for the enterprise tenant is generated. This complete deployment package contains the enterprise tenant's services and the overall real configuration file. Subsequent steps will deploy the services within the complete cluster based on the information in this complete deployment package, providing services to the enterprise tenant.

[0075] This step generates the enterprise tenant deployment package, which is then used in subsequent processes.

[0076] Step 105: Deploy each service application in the tenant's target service information to Kubernetes according to the deployment package.

[0077] Step 105 specifically includes:

[0078] For the configuration information of each service application extracted from the archive repository based on the tenant's target service information: the configuration information is traversed line by line to determine whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application to obtain the complete configuration information of the current service application.

[0079] Based on the preset environment information, each service application is deployed to Kubernetes according to its complete configuration information.

[0080] The operations and maintenance personnel select the enterprise tenant deployment package generated in the previous step, and use the deployment tool to specify the main deployment environment information, including development, testing, pre-release, and production environments. The tool then automatically deploys the package to the cluster. The enterprise tenant deployment process is as follows: Figure 4 As shown.

[0081] The deployment process relies on the deployment package generated by the above steps to clarify the enterprise tenant's services, version numbers, and corresponding deployment or runtime configuration information. The specific process is as follows: Figure 8 As shown.

[0082] Deployment Process: Based on the completed overall configuration file, the complete configuration file for each service is reconstructed and combined into a complete deployment file. This file is then connected to the corresponding cluster and deployment is executed. The reconstruction and combination process is as follows: Figure 9 As shown.

[0083] During the deployment process, the automated deployment tool utilizes the cluster's own Application Program Interface (API) to check whether the deployment has been completely completed. If the cluster API returns a deployment error, or if the deployment fails and restarts abnormally during the deployment process, the deployment will be rolled back to ensure atomicity. This process prevents incorrect configuration information from causing deployment failures that could impact enterprise tenant services, especially during service upgrades. If the deployment is rolled back, the cluster API can return the error information of the deployment failure. After sending this information back to the operations and maintenance personnel, they can check for configuration errors, correct the configuration, and repeat the deployment steps to complete the deployment.

[0084] Compared with existing technologies, this invention improves the automation level of operation and maintenance, enhances deployment efficiency in enterprise multi-tenant environments, and reduces the complexity of operation and maintenance.

[0085] With services as the basic module, operations and maintenance personnel manually fill in the service version list and hand it over to the automatic deployment tool to generate complete configuration information. This allows operations and maintenance to shift from focusing on individual services to focusing on the entire tenant, improving the automation of configuration information. After configuration, the automatic deployment tool can complete the deployment of enterprise tenants with one click, and supports atomicity in the deployment to ensure the integrity and security of the deployment.

[0086] Meanwhile, compared to pipeline technology, this invention encapsulates commonly used operation and maintenance tasks through automated deployment tools, reducing the complexity and learning cost of operation and maintenance.

[0087] Figure 10 This is a schematic diagram of a Kubernetes deployment system architecture according to the present invention, as shown below. Figure 10 As shown, a Kubernetes deployment system includes:

[0088] The tenant target service information determination module 201 is used to obtain tenant target service information based on tenant service requirements. The tenant target service information includes multiple service applications and the version information corresponding to each service application.

[0089] The initial overall configuration file generation module 202 is used to extract the configuration information corresponding to each service application from the archive repository based on the tenant's target service information and generate the initial overall configuration file. The archive repository includes archive information of multiple service applications. The archive information of each service application includes code image, version information and configuration information. The configuration information includes code configuration and cluster configuration. The cluster configuration is the configuration for deploying the service application to Kubernetes.

[0090] The common configuration and differential configuration differentiation module 203 is used to differentiate the configuration information of the initial overall configuration file into common configuration and differential configuration.

[0091] Deployment package build module 204 is used to build tenant deployment packages; the tenant deployment package includes tenant target service information, common configuration and differential configuration.

[0092] The service application deployment module 205 is used to deploy each service application in the tenant's target service information to Kubernetes according to the deployment package.

[0093] The common configuration and differential configuration differentiation module 203 specifically includes:

[0094] The configuration name occurrence count module is used to iterate through the initial overall configuration file line by line and count the occurrences of the configuration name as the key.

[0095] The common configuration and differential configuration differentiation unit is used to classify configuration names that appear once as differential configurations and configuration names that appear more than once as common configurations.

[0096] The storage unit is used to store all common configurations in the common node and store each differential configuration in the differential node named after the corresponding service application.

[0097] The service application deployment module 205 specifically includes:

[0098] The configuration information combination unit is used to extract the configuration information of each service application from the archive repository based on the tenant's target service information: it iterates through the configuration information line by line, determines whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application, thereby obtaining the complete configuration information of the current service application.

[0099] Each service application deployment unit is used to deploy each service application to Kubernetes based on its complete configuration information.

[0100] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to the method section.

[0101] This document uses specific examples to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. Furthermore, those skilled in the art will recognize that, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A Kubernetes deployment method, characterized in that, include: The tenant's target service information is obtained based on the tenant's service requirements. The tenant's target service information includes multiple service applications and version information corresponding to each service application. Based on the tenant's target service information, the configuration information corresponding to each service application is extracted from the archive repository to generate an initial overall configuration file. The archive repository includes archive information for multiple service applications. The archive information for each service application includes code image, version information, and configuration information. The configuration information includes code configuration and cluster configuration. The cluster configuration is the configuration for deploying the service application to Kubernetes. When generating the overall configuration, the values ​​of existing configuration files are merged into the new overall configuration. The configuration information of the initial overall configuration file is divided into common configuration and differential configuration; Construct a tenant deployment package; the tenant deployment package includes the tenant's target service information, the common configuration, and the differential configuration; According to the deployment package, each of the service applications in the tenant target service information is deployed to Kubernetes; The configuration information in the initial overall configuration file is divided into common configuration and differential configuration, specifically including: The initial overall configuration file is traversed line by line, and the configuration name is used as the key to count the number of occurrences. Configuration names that appear once are designated as differential configurations, while configuration names that appear more than once are designated as common configurations. Store all the common configurations in the common node, and store each differential configuration in a differential node named after the corresponding service application name; According to the deployment package, each of the service applications in the tenant target service information is deployed to Kubernetes, specifically including: For the configuration information of each service application extracted from the archive repository based on the tenant target service information: the configuration information is traversed line by line to determine whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application to obtain the complete configuration information of the current service application. Each service application is deployed to Kubernetes based on its complete configuration information.

2. A Kubernetes deployment system, characterized in that, include: The tenant target service information determination module is used to obtain tenant target service information based on tenant service requirements. The tenant target service information includes multiple service applications and version information corresponding to each service application. The initial overall configuration file generation module is used to extract the configuration information corresponding to each service application from the archive repository based on the tenant target service information, and generate the initial overall configuration file. The archive repository includes archive information of multiple service applications. The archive information of each service application includes code image, version information, and configuration information. The configuration information includes code configuration and cluster configuration. The cluster configuration is the configuration for deploying the service application to Kubernetes. When generating the initial overall configuration file, the values ​​of existing configuration files are merged into the initial overall configuration file. The common configuration and differential configuration differentiation module is used to differentiate the configuration information of the initial overall configuration file into common configuration and differential configuration; The deployment package building module is used to build tenant deployment packages; the tenant deployment package includes the tenant target service information, the common configuration, and the differential configuration; Each service application deployment module is used to deploy each of the service applications in the tenant target service information to Kubernetes according to the deployment package; The module for distinguishing between common and differential configurations specifically includes: The configuration name occurrence count module is used to iterate through the initial overall configuration file line by line and count the occurrence count of the configuration name as the key. The common configuration and differential configuration differentiation unit is used to classify configuration names that appear once as differential configurations and configuration names that appear more than once as common configurations. The module for distinguishing between common and differential configurations specifically includes: The storage unit is used to store all the common configurations in the common node and store each differential configuration in the differential node named after the corresponding service application name; The service application deployment modules specifically include: The configuration information combination unit is used to: for each service application configuration information extracted from the archive repository based on the tenant target service information, the configuration information is traversed line by line to determine whether each configuration name is a common configuration or a differential configuration. If the current configuration name is a common configuration, the configuration value of the current configuration name is extracted from the common node. If the current configuration name is a differential configuration, the configuration value of the current configuration name is extracted from the differential node corresponding to the current service application to obtain the complete configuration information of the current service application. Each service application deployment unit is used to deploy each service application to Kubernetes based on the complete configuration information of each service application.

Images