CN117472509A - Non-containerized application management method based on Kubernetes cluster equipment - Google Patents

Abstract

The embodiment of this application provides a non-containerized application management method based on Kubernetes cluster equipment, which relates to the field of cloud computing and is applied to Kubernetes cluster equipment. The Kubernetes cluster equipment includes: at least one Master node, and at least one corresponding to the Master node. Node node; the Master node also includes: non-containerized application NCA controller; the NCA controller includes: application deployment module and application management module; the Node node also includes: non-containerized application agent NCAlet component and non-containerized application; the method includes: Through the application deployment module, the deployment resource update of the non-containerized application is determined, and the state resources of the non-containerized application are updated according to the updated deployment resource configuration parameters; through the application management module, the state resource update is determined and the updated state resource configuration parameters are obtained. ; Update the application status of non-containerized applications according to the updated status resource configuration parameters through the NCAlet component. It can improve the efficiency of operation and maintenance management of non-containerized applications.

Description

Non-containerized application management method based on Kubernetes cluster equipment

Technical field

This application relates to the field of cloud computing technology. Specifically, this application relates to a non-containerized application management method based on Kubernetes cluster equipment.

Background technique

Cloud computing provides an efficient, flexible, and scalable computing resource management method based on resource sharing and on-demand allocation, while containerization technology provides an effective means of deploying and running applications in a cloud environment. With the popularity of cloud computing, more and more applications are gradually moved to the cloud and moved to container clusters.

Using Kubernetes (K8s for short) to manage containerized applications has become a standard. However, due to the existence of various complex business systems and technology stacks, there are still many applications that cannot be containerized. Currently, such non-containerized applications usually require manual management. Manual management is error-prone and requires high staff capabilities and management efficiency. Problems such as inferiority.

In this case, there is an urgent need to provide a non-containerized application management solution to achieve efficient management of non-containerized applications.

Contents of the invention

The purpose of this application is to solve at least one of the above technical defects. The technical solutions provided by the embodiments of this application are as follows:

In the first aspect, embodiments of this application provide a non-containerized application management method based on Kubernetes cluster equipment, which is applied to Kubernetes cluster equipment;

Among them, the Kubernetes cluster equipment includes: at least one Master node and at least one Node node corresponding to the Master node;

The Master node also includes: non-containerized application NCA controller;

The NCA controller includes: application deployment module and application management module;

Node nodes also include: non-containerized application agent NCAlet components and non-containerized applications;

Methods include:

Through the application deployment module, determine the deployment resource update of the non-containerized application, and update the status resources of the non-containerized application according to the updated deployment resource configuration parameters;

Through the application management module, determine the status resource update and obtain the updated status resource configuration parameters;

Through the NCAlet component, the application status of the non-containerized application is updated according to the updated status resource configuration parameters.

In an optional embodiment of the present application, the method further includes:

Define the deployment resource template and status resource template of non-containerized applications in the Kubernetes cluster device by customizing resource definitions.

In an optional embodiment of the present application, the method further includes:

Through the application deployment module, the initial deployment resource configuration parameters are obtained, and the status resources of the non-containerized application are updated according to the initial deployment resource configuration parameters.

In an optional embodiment of this application, determining deployment resource updates for non-containerized applications specifically includes:

Monitor the deployment resource configuration parameters of the non-containerized application. If it is determined that at least one of the deployment resource deletion, deployment resource copy configuration change and deployment resource version change has occurred in the deployment resource of the non-containerized application, determine the deployment resource of the non-containerized application. renew.

In an optional embodiment of the present application, the method specifically includes:

Through the application deployment module, it is determined that the deployment resources of the non-containerized application have changed in deployment resource deletion, and the state resources of the non-containerized application are correspondingly deleted;

Through the application management module, determine the state resource deletion of the non-containerized application and call the NCAlet component corresponding to the non-containerized application;

Remove non-containerized applications from Kubernetes cluster devices through the NCAlet component.

In an optional embodiment of the present application, the method specifically includes:

Through the application deployment module, it is determined that the deployment resource copy configuration of the non-containerized application has changed, the updated deployment resource copy configuration parameters are obtained, and the state resource copy configuration parameters of the non-containerized application are updated according to the updated deployment resource copy configuration parameters. ;

Through the application management module, determine the state resource update and obtain the updated state resource copy configuration parameters;

Through the NCAlet component, the corresponding non-containerized application copy is deleted and/or added based on the updated state resource copy configuration parameters.

In an optional embodiment of the present application, the method further includes:

Through the application deployment module, it is determined that the deployment resource version of the non-containerized application has changed, and the status resource version of the non-containerized application is updated according to the updated deployment resource version configuration parameters;

Through the application management module, determine the status resource update and obtain the updated status resource version configuration parameters;

Through the NCAlet component, the version of the non-containerized application is updated according to the updated state resource version configuration parameters.

In the second aspect, embodiments of this application provide a Kubernetes cluster device. The Kubernetes cluster device includes: at least one Master node, and at least one Node node corresponding to the Master node;

The Master node also includes: non-containerized application NCA controller;

The NCA controller includes: application deployment module and application management module;

Node nodes also include: non-containerized application agent NCAlet components and non-containerized applications;

Among them, the application deployment module is used to determine the deployment resource update of the non-containerized application, and update the status resources of the non-containerized application according to the updated deployment resource configuration parameters;

The application management module is used to determine status resource updates and obtain updated status resource configuration parameters;

The NCAlet component is used to update the application status of non-containerized applications based on the updated status resource configuration parameters.

In the third aspect, embodiments of the present application provide an electronic device. The electronic device includes a memory, a processor, and a computer program stored on the memory. The processor executes the computer program to implement the Kubernetes-based cluster provided in any of the above embodiments. Steps for a device's non-containerized application management approach.

In the fourth aspect, embodiments of the present application provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the non-containerized application based on the Kubernetes cluster device provided in any of the above embodiments is implemented. management methods.

The beneficial effects brought by the technical solutions provided by the embodiments of this application are:

This solution incorporates non-containerized applications into the Kubernetes ecosystem by introducing non-containerized application NCA controller and non-containerized application agent NCAlet components into Kubernetes cluster equipment. Unified management of containerized and non-containerized applications can be achieved through Kubernetes. , reduce the complexity of management and improve the efficiency of operation and maintenance management of non-containerized applications.

Description of the drawings

In order to explain the technical solutions in the embodiments of the present application more clearly, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below.

Figure 1 is a flow chart of a non-containerized application management method based on Kubernetes cluster equipment provided by an embodiment of the present application;

Figure 2 is one of the schematic diagrams of the architecture of an application operation and maintenance management platform provided by an embodiment of the present application;

Figure 3 is a second schematic diagram of the architecture of an application operation and maintenance management platform provided by an embodiment of the present application;

Figure 4 is a schematic flow chart of a non-containerized application management method based on Kubernetes cluster equipment provided by the embodiment of the present application;

Figure 5 is a schematic structural diagram of a Kubernetes cluster device provided by an embodiment of this application;

FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application are described below with reference to the drawings in the present application. It should be understood that the embodiments described below in conjunction with the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application, and do not limit the technical solutions of the embodiments of the present application.

Those skilled in the art will understand that, unless expressly stated otherwise, the singular forms "a", "an", "the" and "the" used herein may also include the plural form. It should be further understood that the terms "comprising" and "including" used in the embodiments of this application mean that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements and/or components, but do not exclude Implementation is other features, information, data, steps, operations, elements, components and/or their combinations supported by the technical field. It should be understood that when we refer to an element being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or one element and the other element may be connected to the other element through intervening elements. Establish connections. Additionally, "connected" or "coupled" as used herein may include wireless connections or wireless couplings. The term "and/or" is used herein to indicate at least one of the items defined by the term. For example, "A and/or B" can be implemented as "A", or as "B", or as "A and B" ".

In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The following describes the terms and related technologies involved in this application:

Kubernetes (hereinafter referred to as K8s) is an open source container orchestration tool used to automate the deployment, expansion and management of applications. K8s provides a unified way to manage containerized applications, ensuring that applications run efficiently in distributed environments.

A Kubernetes cluster (hereinafter referred to as a K8s cluster) refers to a collection of multiple devices that are configured to run K8s together to create and manage containerized applications. In a K8s cluster, at least one Master node (i.e., control node) is set up to manage the status and task distribution of the entire cluster, while the Node node (i.e., working node) corresponding to the Master node is responsible for performing specific work tasks.

Figure 2 is one of the schematic diagrams of an application operation and maintenance management platform architecture provided by an embodiment of the present application. Taking the application operation and maintenance management platform shown in Figure 2 as an example, the actual application architecture of K8s in the prior art is explained. This application The operation and maintenance management platform architecture is built based on K8s cluster, supports the full life cycle management of containerized applications on the cloud, and also provides other functional services, such as application scaling, health check, fault recovery, etc.

Among them, the Master node is responsible for managing the status and configuration information of the entire K8s cluster. It runs multiple core components, including the Application Program Interface Server (API server or API Server), distributed key-value storage ( ETCD), controller (Controller) and scheduler (Scheduler), etc., are used to coordinate and manage various resources in the cluster.

The API server serves as the front-end interface of the cluster, receiving API (ApplicationProgram Interface, application program interface) requests from users and other components, and forwarding them to the corresponding module for processing.

ETCD is used to store cluster configuration information, status data, and metadata to ensure cluster consistency.

The Controller is responsible for monitoring the status changes of resource objects in the cluster and adjusting and maintaining them according to predefined rules.

Scheduler is responsible for scheduling newly created Pods to run on appropriate Node nodes based on predefined conditions and policies.

Node is a machine that runs K8s workload, mainly including node agent (Kubelet), container group (Pod), container runtime (Container Runtime), network proxy (network-proxy) and optional add-ons (optional add-ons), etc. , used to host the actual operation of the container.

Kubelet is responsible for communicating with the Master node, receiving instructions from the Master node and managing containers on the node.

Pod is the smallest schedulable and manageable deployment unit in K8s. A Pod represents a process running in the cluster and is a collection of one or more related containers running on the same host.

Container Runtime is the software component responsible for creating, running and managing containers on the host.

Network-Proxy is a K8s component responsible for managing network traffic and routing traffic to the correct Pod.

Optional add-ons are used to extend basic functionality. For example, the DNS plug-in provides service discovery and name resolution functions, and the UI plug-in provides a Web-based user interface, making cluster management, monitoring, and operation more intuitive, simple, and easy to use.

It is understandable that in the K8s cluster architecture, a Master node is usually set up to manage the status and task distribution of the entire cluster. However, considering actual application requirements, multiple Master nodes can be set up to improve high availability (HighAvailability, HA). When using a single Master node, if the Master node fails, the entire cluster will not be able to operate normally. The introduction of multiple Master nodes can improve the fault tolerance and reliability of the cluster.

The following describes the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application through the description of several exemplary embodiments. It should be noted that the following embodiments can be referred to, borrowed from, or combined with each other. The same terms, similar features, and similar implementation steps in different embodiments will not be repeatedly described.

Figure 1 is a flow chart of a non-containerized application management method based on Kubernetes cluster equipment provided by an embodiment of the present application. As shown in Figure 1, an embodiment of the present application provides a non-containerized application management method based on Kubernetes cluster equipment. The method is applied to Kubernetes cluster equipment, where the Kubernetes cluster equipment includes: at least one Master node and at least one Node node corresponding to the Master node;

The Master node also includes: non-containerized application NCA controller;

The NCA controller includes: application deployment module and application management module;

Node nodes also include: non-containerized application agent NCAlet components and non-containerized applications.

Specifically, Figure 3 is the second schematic diagram of an application operation and maintenance management platform architecture provided by an embodiment of the present application. Taking the application operation and maintenance management platform shown in Figure 3 as an example, the actual application architecture of the improved K8s cluster device in this embodiment is For explanation, see Figure 2 and Figure 3. The improved K8s cluster device provided in this embodiment adds a non-containerized application NCA (non-containerized applications Controller, non-containerized application) based on the existing K8s cluster device. Application) controller, non-containerized application agent NCAlet component and non-containerized application NCA.

Among them, the NCA controller is a component in the Master node and is responsible for non-containerized application deployment and management. The NCA controller includes an application deployment module and an application management module.

The application deployment module is used to monitor changes in the deployment resources of non-containerized applications, and complete synchronous modification of the status resources of non-containerized applications based on changes in deployment resource configuration parameters.

The application management module is used to monitor changes in state resources of non-containerized applications and call the NCAlet component based on changes in state resource configuration parameters.

The NCAlet component provides management capabilities and consistent state synchronization capabilities for non-container applications. Based on the updated status resource configuration parameters, corresponding scheduling operations are performed according to the preset scheduling rules to update the application status of non-containerized applications.

It is understandable that the management capabilities provided by the NCAlet component include environment dependency checking, installation media download, application deployment, and application startup and stop after installation is completed. It can also implement non-container application health check, fault recovery and other functions on the node. . Furthermore, implementation interfaces can be provided to facilitate access to management capabilities of various applications.

It is understandable that resource (deployment resources and status resources) templates need to be pre-defined in the improved K8s cluster. The resource configuration parameters submitted by operation and maintenance personnel are based on the resource template. The resource template setting method and the specific content of the resource template can be Determine based on actual needs.

For example, the resource template specifically includes the list of hosts that need to be deployed, application types, related startup scripts, stop scripts, and related configurations about health checks.

In addition, the preset scheduling rules are used to instruct the NCAlet component to complete corresponding scheduling operations according to specific changes in status resources. The specific content of the preset scheduling rules can be set according to actual needs.

Correspondingly, non-containerized application management methods based on Kubernetes cluster devices include:

Step S101: Determine the deployment resource update of the non-containerized application through the application deployment module, and update the status resources of the non-containerized application according to the updated deployment resource configuration parameters.

Specifically, when the operation and maintenance personnel change the deployment resource configuration of the non-containerized application, they submit the deployment resource configuration parameters to the API Server of the Kubernetes cluster device. In step S101, the application deployment module monitors the deployment of non-containerized applications in the API Server. Whether the resources are updated (changed), when the application deployment module monitors the deployment resource update, obtains the updated deployment resource configuration parameters, and synchronously updates the corresponding non-containerized application status resources according to the deployment resource configuration parameters.

Step S102: Use the application management module to determine status resource updates and obtain updated status resource configuration parameters.

Specifically, in step S102, the application management module monitors whether the status resource of the non-containerized application is updated (changed). When the application management module monitors the status resource update, it obtains the updated status resource configuration parameters and calls the NCAlet component.

Step S103: Update the application status of the non-containerized application according to the updated status resource configuration parameters through the NCAlet component.

Specifically, in step S103, the NCAlet component completes the corresponding scheduling operation with the preset scheduling rules according to the updated status resource configuration parameters, and implements the application status update of the non-containerized application to ensure the deployment resources and deployment of the non-containerized application. State resource consistency.

Through the non-containerized application management method provided in this embodiment, the non-containerized application life cycle can be managed in a cloud-native manner through the unified entry kubectl command, and the cloud application (containerized application) and non-containerized application can be completed within the enterprise. Unified management of applications. Among them, containerized applications can include virtual machine applications and physical machine applications.

In the actual operation and maintenance management process, operation and maintenance personnel can operate the K8s API Server by executing kubectl commands to complete the management of the non-containerized application life cycle and improve operation and maintenance efficiency. The method provided in this embodiment is based on convenient management. At the same time, non-containerized applications have some features of cloud applications, such as health check, fault recovery, etc.

The technical solution provided by the embodiment of this application incorporates non-containerized applications into the Kubernetes ecosystem by introducing non-containerized application NCA controller and non-containerized application agent NCAlet components into Kubernetes cluster equipment, and can realize containerized applications and non-containerized applications through Kubernetes. Unified management of containerized applications reduces management complexity and improves the efficiency of operation and maintenance management of non-containerized applications.

In an optional embodiment of the present application, the method further includes:

Define the deployment resource template and status resource template of non-containerized applications in the Kubernetes cluster device by customizing resource definitions.

Specifically, K8s provides an extension mechanism to operation and maintenance personnel (i.e. users). The CRD (Custom Resource Definition) mechanism is a way of extending the API provided by K8s, allowing operation and maintenance personnel to use existing K8s resources (such as Resource objects Deployment and Configmap in K8s, etc.) customize resource types. Custom resource types can be managed like K8s native resources, giving operation and maintenance personnel the ability to expand application management in K8s clusters.

The technical solution provided in this embodiment uses custom resource definition to define the deployment resource template and status resource template of non-containerized applications in the Kubernetes cluster device.

It is understandable that deployment resource templates and status resource templates are a custom resource type used to describe the resources required by non-containerized applications. The corresponding specifications need to be customized through the CRD mechanism and programs written to achieve NCA The controller and NCAlet components monitor the complete life cycle management of deployment resources and status resources (such as events such as creation, update, and deletion), and perform corresponding scheduling operations according to preset scheduling rules.

For example, through CRD mechanism customization, a declarative API is used to create related resources NCA CR (Non-Containerized Applications Custom Resource) required for non-containerized application management. NCA CR includes non-containerized applications. The application's deployment resource template and state resource template.

Deployment resources are used to define the creation, update, and deletion of application replica sets. Deployment resource templates can include the target host for application deployment, the running environment, the address of the deployment media, etc. State resources are used to manage stateful applications. State resource templates can include the application's replica set, unique identifiers of replicas, network identifiers, etc.

Correspondingly, the operator is used to add the scheduling logic corresponding to the NCA controller and NCAlet component to K8s to realize the monitoring of the Kubernetes API object corresponding to the custom resource and the change of the NCA CR object (the operation and maintenance personnel complete the NCA by operating the kubectl command Perform scheduling operations corresponding to the preset scheduling rules when creating, updating, deleting CRs, etc.).

It can be understood that the specific details and field definitions of deployment resource templates and status resource templates, as well as the specific programming content of the program and the specific settings of the preset scheduling rules, can be freely defined according to actual needs.

The technical solution provided by the embodiment of this application customizes the resource definition mechanism through the expansion mechanism of the Kubernetes cluster, defines the deployment resource template and status resource template in the Kubernetes cluster device, and ensures the deployment of resources by setting the NCA controller and NCAlet components and corresponding programs. and state resource consistency, and realize the scheduling operation of non-containerized applications, improve the efficiency of operation and maintenance management of non-containerized applications, realize the unified management of containerized applications and non-containerized applications, and reduce the complexity of management.

In an optional embodiment of the present application, the method further includes:

Through the application deployment module, the initial deployment resource configuration parameters are obtained, and the status resources of the non-containerized application are updated according to the initial deployment resource configuration parameters.

Specifically, after completing the definition of deployment resource templates and status resource templates, for the first management of non-containerized applications on the K8s cluster, an initial information synchronization is required, that is, the initial deployment resource configuration parameters are obtained through the application deployment module. , and update the status resources of the non-containerized application based on the initial deployment resource configuration parameters to ensure that they are consistent with the actual deployment resource configuration.

Furthermore, based on the NCA controller and NCAlet component, the scheduling mechanism is implemented according to the preset scheduling rules. When the application management module monitors the status resource update, it obtains the updated status resource configuration parameters and calls the NCAlet component. According to the updated status Resource configuration parameters to update the application status of non-containerized applications.

The technical solution provided by the embodiment of this application obtains the initial deployment resource configuration parameters through the application deployment module, corresponding to the update of the status resource configuration parameters and the application status update of the non-containerized application, and incorporates the non-containerized application into the Kubernetes ecosystem, which can be done through Kubernetes Achieve comprehensive management and monitoring of the containerized application life cycle, reduce management complexity, and make the deployment and management of non-containerized applications more flexible and efficient.

In an optional embodiment of this application, determining deployment resource updates for non-containerized applications specifically includes:

Monitor the deployment resource configuration parameters of the non-containerized application. If it is determined that at least one of the deployment resource deletion, deployment resource copy configuration change and deployment resource version change has occurred in the deployment resource of the non-containerized application, determine the deployment resource of the non-containerized application. renew.

Specifically, changes in deployment resources for non-containerized applications include: deployment resource deletion, deployment resource copy configuration changes, and deployment resource version changes. Based on the above three changes, in this embodiment, preset scheduling rules are determined according to actual needs, and different scheduling operations are set for different types of changes.

It can be understood that the scheduling operation instructions are used to schedule the NCAlet component to complete the corresponding scheduling operations. "First", "second" and "third" are only used to distinguish different types of scheduling operation instructions in this application and do not limit the scheduling operations. The specific content of the instruction.

Among them, deployment resource deletion refers to completely deleting the deployment resources corresponding to the non-containerized application that has been deployed in the K8s cluster, that is, completely removing a non-containerized application, including all copies and related configurations corresponding to the non-containerized application, etc. .

Deployment resource copy configuration changes refer to changing the copy configuration of deployment resources corresponding to non-containerized applications that have been deployed in the K8s cluster. By modifying the copy configuration, you can adjust the scale, configuration and functions of the non-containerized application in the K8s cluster. . The replica configuration can include the number of replicas, container port and other related parameters.

It is understandable that, considering the high availability and load balancing requirements of applications, applications are often deployed in multiple copies. At this time, copy deletion refers to removing one or more copies, but still keeping other copies running. Removal is typically done to adjust the application's scalability or performance needs, or to handle failures or upgrades.

Deleting the deployment resources of a non-containerized application corresponds to deleting the entire non-containerized application from the K8s cluster, which means that all components and data of the application will be deleted (including all corresponding copies), and the application will no longer be available. When deleting a copy corresponding to a change in the deployment resource copy configuration of a non-containerized application, the corresponding copy of the application is deleted from the K8s cluster, and other copies are still available, instead of deleting the entire application.

Deploying resource version changes refers to upgrading or updating the corresponding version of a non-containerized application that has been deployed in the K8s cluster. It usually involves creating a new version of the non-containerized application and deploying it to the K8s cluster. The new version may involve bug fixes, feature enhancements or performance improvements and other changes to the original version.

Use the application deployment module to determine whether the deployment resource configuration parameters of the non-containerized application have changed. If it is determined that the deployment resource configuration parameters have changed, for example, at least one of deployment resource deletion, deployment resource copy configuration change, and deployment resource version change. , then determine the deployment resource update of the non-containerized application.

Furthermore, based on the NCA controller and NCAlet components, the updated deployment resource configuration parameters are used to determine the updated status resource configuration parameters, and the scheduling mechanism implemented based on the preset scheduling rules is used to determine the specific type of deployment resource update and the updated status. Resource configuration parameters, correspondingly update the application status of non-containerized applications to ensure that they are consistent with the actual deployment resource configuration.

It can be understood that the application deployment module is used to monitor the deployment resources of non-containerized applications. The application deployment module can determine the specific type of deployment resource changes based on changes in deployment resource configuration parameters. Correspondingly, the application management module is used to monitor non-containerized applications. The state resources of containerized applications and the application management module can determine the specific types of state resource changes (corresponding to changes in deployment resources) based on changes in state resource configuration parameters. The specific program writing and implementation methods can be determined according to actual needs.

The technical solution provided by the embodiment of this application uses the application deployment module to monitor deployment resources and determine whether three types of deployment resource changes have occurred: deployment resource deletion, deployment resource copy configuration change, and deployment resource version change. It can be targeted based on non-containerized applications. The specific type of deployment resource update triggers the execution of corresponding scheduling operations, realizing automated and refined non-containerized application operation and maintenance, and improving the controllability and stability of the operation and maintenance process.

In an optional embodiment of the present application, the method specifically includes:

Through the application deployment module, it is determined that the deployment resources of the non-containerized application have changed in deployment resource deletion, and the state resources of the non-containerized application are correspondingly deleted;

Through the application management module, determine the state resource deletion of the non-containerized application and call the NCAlet component corresponding to the non-containerized application;

Remove non-containerized applications from Kubernetes cluster devices through the NCAlet component.

Specifically, the application deployment module monitors the deployment resources. If it is determined through the application deployment module that the deployment resources of the non-containerized application have been changed by deleting the deployment resources, the status resources will be updated synchronously according to the changes in the deployment resources, corresponding to the status of the non-containerized application. Resource deletion.

The application management module monitors state resources. If the application management module determines that the state resource of the non-containerized application has been deleted, it calls the NCAlet component corresponding to the non-containerized application and delivers the first scheduling operation instruction corresponding to the state resource deletion.

The NCAlet component receives the corresponding first scheduling operation instruction, determines the corresponding non-containerized application, stops and deletes it on the K8s cluster device.

The technical solution provided by the embodiment of this application uses the application deployment module to monitor deployment resources. After it is determined that the deployment resource is deleted, the state resources and the corresponding non-containerized applications are deleted in a targeted manner. The deletion process of the entire non-containerized application is automatically triggered. , without the need for operation and maintenance personnel to intervene, saving the time and energy of operation and maintenance personnel, avoiding human negligence and errors, while improving operation and maintenance efficiency, and ensuring the consistency of non-containerized application deployment resources, status resources and application status sex.

In an optional embodiment of the present application, the method specifically includes:

Through the application deployment module, it is determined that the deployment resource copy configuration of the non-containerized application has changed, the updated deployment resource copy configuration parameters are obtained, and the state resource copy configuration parameters of the non-containerized application are updated according to the updated deployment resource copy configuration parameters. ;

Through the application management module, determine the state resource update and obtain the updated state resource copy configuration parameters;

Through the NCAlet component, the corresponding non-containerized application copy is deleted and/or added based on the updated state resource copy configuration parameters.

Specifically, the application deployment module monitors the deployment resources. If it is determined through the application deployment module that the deployment resources of the non-containerized application have changed the deployment resource copy configuration, it will obtain the updated deployment resource copy configuration parameters based on the deployment resource copy configuration changes. After the resource copy configuration parameters are deployed, the status resource copy configuration parameters are synchronously updated.

The application management module monitors state resources. If the application management module determines that the state resource copy configuration parameters of the non-containerized application have changed, it obtains the updated state resource copy configuration parameters, calls the corresponding NCAlet component, and passes the copy configuration change response The second scheduling operation instruction.

The NCAlet component receives the corresponding second scheduling operation instruction, determines the corresponding non-containerized application copy, and completes the copy configuration.

It can be understood that the copy configuration includes the deletion and/or addition of corresponding non-containerized application copies (including the simultaneous deletion of some copies and the addition of some copies) to ensure the number of copies and copy deployment of non-containerized applications. , consistent with the deployment resource copy configuration parameters, the specific scheduling operation type and implementation method can be determined according to actual needs.

The technical solution provided by the embodiments of this application uses the application deployment module to monitor deployment resources. After determining that a deployment resource copy configuration change has occurred, the state resource copy configuration parameters are updated according to the updated deployment resource copy configuration parameters, and further delete and/or add new ones. For corresponding non-containerized application copies, the entire copy management process is automatically triggered, which can flexibly adapt to copy expansion, maintenance, fault handling, etc., facilitate the management of non-containerized applications, and effectively improve operation and maintenance efficiency.

In an optional embodiment of the present application, the method further includes:

Through the application deployment module, it is determined that the deployment resource version of the non-containerized application has changed, and the status resource version of the non-containerized application is updated according to the updated deployment resource version configuration parameters;

Through the application management module, determine the status resource update and obtain the updated status resource version configuration parameters;

Through the NCAlet component, the version of the non-containerized application is updated according to the updated state resource version configuration parameters.

Specifically, the purpose of version updates for non-containerized applications is to meet needs such as introducing new features, fixing bugs, improving performance, or responding to security vulnerabilities. This embodiment provides a solution for automatically updating non-containerized application versions by updating deployment resources.

The application deployment module monitors the deployment resources. If it is determined through the application deployment module that the deployment resource version of the non-containerized application has changed, it will obtain the updated deployment resource version configuration parameters based on the deployment resource version change. According to the updated deployment resource version Configuration parameters synchronize and update status resource version configuration parameters.

The application management module monitors the status resources. If it is determined through the application management module that the status resource version configuration parameters of the non-containerized application have changed, it will obtain the updated status resource version configuration parameters, call the corresponding NCAlet component, and pass the version corresponding to the change. The third scheduling operation instruction.

The NCAlet component receives the corresponding third scheduling operation instruction, determines the corresponding non-containerized application, and updates the version of the non-containerized application according to the updated status resource version configuration parameters.

The technical solution provided by the embodiments of this application uses the application deployment module to monitor deployment resources. After determining that a deployment resource version configuration change has occurred, the status resource version configuration parameters are updated according to the updated deployment resource version configuration parameters, and further the non-containerized application is processed. Version update: Compared with the traditional method of manually deploying a new version of an application, this embodiment can automatically update the application version, simplify the deployment process, reduce the operation and burden of operation and maintenance personnel, and ensure that the deployment resources and status resources are consistent with the new version. Matching avoids data inconsistencies or abnormal states caused by version updates, making the process of updating versions more efficient, reliable and controllable, facilitating the management of non-containerized applications, and effectively improving operation and maintenance efficiency and application stability.

The specific application of the embodiments of this application will be described in detail below through a specific example:

Figure 4 is a schematic flow chart of a non-containerized application management method based on Kubernetes cluster equipment provided by the embodiment of the present application. As shown in Figure 4, after completing the deployment of resource templates and status resource templates (which may include deployment target hosts, application types , installation media, application ports, deployment paths, etc.) in the K8s cluster device, as well as the preset scheduling rules and program specific writing content corresponding to the NCA controller and NCAlet components (which can include startup scripts, stop scripts, and health check-related configurations etc.), operation and maintenance personnel can implement operation and maintenance management of non-containerized applications based on K8s cluster devices.

When operation and maintenance personnel need to change the configuration of a non-containerized application, use a command line tool (such as kubectl) to create a resource configuration file corresponding to the non-containerized application deployment resource, define the resource objects to be deployed, and send the resource configuration file to In the API server, the API server completes the configuration of the deployed resources based on the resource configuration file. If the configuration is completed, it is determined that the resource apply is completed.

The application deployment module monitors (i.e., watches) the deployment resources in the API server, and determines the change type of the deployment resources when it is determined that the deployment resources have been updated.

It can be understood that changes in deployment resources for non-containerized applications include: deployment resource deletion, deployment resource copy configuration changes, and deployment resource version changes. When judging a specific type, you can judge whether corresponding changes have occurred at the same time, or use the sequential judgment method shown in Figure 4 to judge whether corresponding changes have occurred in sequence. Furthermore, you can also set priorities for different types. When a certain change occurs, no subsequent changes will be made (for example, if the deployment resource is determined to be deleted, no subsequent judgment will be made). The specific way to determine the type of deployment resource change can be determined based on actual needs.

After the application management module detects the status resource update, it updates the corresponding status resource according to the updated deployment resource, and determines the status resource change type (corresponding to the deployment resource change type). It can be understood that the specific method for judging the change type of state resources is similar to the method for judging the type of change of deployment resources mentioned above, and can be determined according to actual needs.

The application management module calls the NCAlet component to complete the synchronization of the application status of non-containerized applications according to the status resource change type.

If it is determined that the state resource change type is state resource deletion, the NCAlet component is scheduled to stop and delete the corresponding non-containerized application. If the status resource configuration parameters (such as copy configuration parameters and/or version configuration parameters) change, the corresponding scheduling NCAlet component deletes and/or adds applications, and/or updates the application version.

For example, if it is determined that the number of copies corresponding to a non-containerized application has decreased, the NCAlet component is scheduled to stop and the corresponding copies are deleted. If it is determined that the number of copies corresponding to the non-containerized application has increased, the NCAlet component is scheduled to add new copies according to the configuration parameters corresponding to the new copies.

It should be noted that there may be a situation where the number of reduced replicas is the same as the number of new replicas. In this case, the number of replicas remains unchanged. Then the NCAlet component is scheduled to add replicas according to the configuration parameters corresponding to the new replicas, and according to the configuration corresponding to the reduced replicas. parameters, hard and delete the corresponding copy.

It can be understood that deleting the deployment resources of a non-containerized application corresponds to deleting the entire non-containerized application from the K8s cluster, which means that all components and data of the application will be deleted (including all corresponding copies), and the application will no longer be available. Available again. When deleting a copy corresponding to a change in the deployment resource copy configuration of a non-containerized application, the corresponding copy of the application is deleted from the K8s cluster, and other copies are still available, instead of deleting the entire application.

If it is determined that the state resource version configuration parameters have changed, the NCAlet component is scheduled to update the application version of the non-containerized application according to the updated state resource version configuration parameters.

Compared with the existing non-containerized application management methods of manual management, development script management and configuration tool management:

The manual management method requires operation and maintenance personnel to have corresponding skills and has high requirements for operation and maintenance personnel. Moreover, due to the different skill levels and habits of different operation and maintenance personnel, it will cause differences in application deployment, and there is a risk of operational errors, which will affect the efficiency of operation and maintenance management. Low.

The technical solution provided by the embodiments of this application can ensure the consistency of application deployment and application status through automated updates. Whether it is the deletion of an application or copy, the deployment of a new copy, or a version upgrade, the correctness and consistency of the application status can be maintained. , avoid manual operations and human errors, and effectively improve the efficiency of application deployment and management.

To develop script management and configuration tool management, you need to use shell scripts (a command language used to execute commands in batches in Unix or Linux systems to achieve automation tasks) or ansible or saltstack (common configuration management tools for automation) Configuration tools such as deploying, configuring and managing infrastructure such as servers, virtual machines and containers) perform management operations through configuration templates in an agreed format.

Although compared with manual management, the efficiency of operation and maintenance management has been improved to a certain extent, because scripts and configuration tool templates still need to be written by operation and maintenance personnel, and different operation and maintenance personnel have different writing habits. There is a lack of unified management, reliability and Consistency is difficult to guarantee, and it takes a lot of time to verify the effects of scripts and configuration tool templates. If the operating system environment is changed, all operations may need to be verified again. After the application is deployed, there is no unified application management entrance, making it difficult to implement Automatic updating and status monitoring of application status, operation and maintenance management are inefficient.

The technical solution provided by the embodiments of this application incorporates non-containerized applications into the Kubernetes ecosystem. Unified management of containerized applications and non-containerized applications can be achieved through Kubernetes. Based on the NCA controller and NCAlet components, the deployment resources of non-containerized applications can be monitored. , and when deploying resource updates, it can realize automatic updates of status resources and application status, maintain the consistency of application deployment and application status, reduce the complexity of management, and improve the efficiency of operation and maintenance management of non-containerized applications.

Figure 5 is a schematic structural diagram of a Kubernetes cluster device provided by an embodiment of the present application. As shown in Figure 5, the Kubernetes cluster device 50 includes: at least one Master node 510, and at least one Node node 520 corresponding to the Master node;

The Master node also includes: non-containerized application NCA controller 511;

The NCA controller includes: application deployment module 5111 and application management module 5112;

The Node node also includes: non-containerized application agent NCAlet component 521 and non-containerized application 522;

Among them, the application deployment module 5111 is used to determine the deployment resource update of the non-containerized application, and update the status resources of the non-containerized application according to the updated deployment resource configuration parameters;

The application management module 5112 is used to determine status resource updates and obtain updated status resource configuration parameters;

The NCAlet component 521 is used to update the application status of the non-containerized application 522 according to the updated status resource configuration parameters.

The technical solution provided in this embodiment incorporates non-containerized applications into the Kubernetes ecosystem by introducing non-containerized application NCA controller and non-containerized application agent NCAlet components into Kubernetes cluster equipment, and can realize containerized applications and non-containerized applications through Kubernetes Unified management of containerized applications reduces management complexity and improves the efficiency of operation and maintenance management of non-containerized applications.

The device of the embodiment of the present application can execute the method provided by the embodiment of the present application, and its implementation principle is similar. The actions performed by each module in the device of the embodiment of the present application are the same as the steps in the method of the embodiment of the present application. Correspondingly, for the detailed functional description of each module of the device, please refer to the description in the corresponding method shown above, and will not be described again here.

In an optional embodiment of this application, deployment resource templates and status resource templates for non-containerized applications are defined in the Kubernetes cluster device; the deployment resource templates and status resource templates are defined through custom resource definitions.

In an optional embodiment of the present application, the application deployment module is also used to obtain initial deployment resource configuration parameters, and update the status resources of the non-containerized application according to the initial deployment resource configuration parameters.

In an optional embodiment of the present application, the application deployment module is also used to monitor the deployment resource configuration parameters of the non-containerized application. If it is determined that the deployment resource of the non-containerized application has been deleted, deployed resource copy configuration changes and deployment If at least one of the resource version changes occurs, the deployment resource update of the non-containerized application is determined.

In an optional embodiment of the present application, the application deployment module is also used to determine that the deployment resources of the non-containerized application have undergone deployment resource deletion changes, and correspondingly delete the status resources of the non-containerized application;

The application management module is also used to determine the state resource deletion of non-containerized applications and call the NCAlet component corresponding to non-containerized applications;

The NCAlet component is also used to remove non-containerized applications from Kubernetes cluster devices.

In an optional embodiment of the present application, the application deployment module is also used to determine that the deployment resources of the non-containerized application have changed the deployment resource copy configuration, obtain the updated deployment resource copy configuration parameters, and obtain the updated deployment resource copy configuration parameters according to the updated deployment resource copy. Configuration parameters update the state resource copy configuration parameters of non-containerized applications;

The application management module is also used to determine status resource updates and obtain updated status resource copy configuration parameters;

The NCAlet component is also used to delete and/or add corresponding non-containerized application copies based on the updated state resource copy configuration parameters.

In an optional embodiment of the present application, the application deployment module is also used to determine that the deployment resource version of the non-containerized application has changed, and update the status resource version of the non-containerized application according to the updated deployment resource version configuration parameters. ;

The application management module is also used to determine status resource updates and obtain updated status resource version configuration parameters;

The NCAlet component is also used to update the version of the non-containerized application based on the updated state resource version configuration parameters.

An embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory. The processor executes the above computer program to implement the steps of the above non-containerized application management method based on Kubernetes cluster equipment, Compared with related technologies, it can be achieved: By introducing non-containerized application NCA controller and non-containerized application agent NCAlet components into Kubernetes cluster equipment, non-containerized applications can be incorporated into the Kubernetes ecosystem, and containerized applications and non-containerized applications can be implemented through Kubernetes. Unified management of containerized applications reduces management complexity and improves the efficiency of operation and maintenance management of non-containerized applications.

In an optional embodiment, an electronic device is provided. FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As shown in FIG. 6 , the electronic device 60 includes: a processor 601 and a memory 603. Among them, the processor 601 and the memory 603 are connected, such as through a bus 602. Optionally, the electronic device 60 may also include a transceiver 604, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and/or data reception. It should be noted that in practical applications, the number of transceivers 604 is not limited to one, and the structure of the electronic device 60 does not constitute a limitation on the embodiments of the present application.

The processor 601 can be a CPU (Central Processing Unit, central processing unit), a general-purpose processor, a DSP (Digital Signal Processor, digital signal processor), ASIC (Application Specific Integrated Circuit, application specific integrated circuit), FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with this disclosure. The processor 601 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

Bus 602 may include a path that carries information between the above-mentioned components. The bus 602 may be a PCI (Peripheral Component Interconnect, Peripheral Component Interconnect Standard) bus or an EISA (Extended Industry Standard Architecture, Extended Industry Standard Architecture) bus, or the like. The bus 602 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 6, but it does not mean that there is only one bus or one type of bus.

The memory 603 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory, random access memory) or other types that can store information and instructions. Dynamic storage devices can also be EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact DiscRead Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, Laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other media that can be used to carry or store computer programs and can be read by a computer, are not limited here.

The memory 603 is used to store computer programs for executing embodiments of the present application, and is controlled by the processor 601 for execution. The processor 601 is used to execute the computer program stored in the memory 603 to implement the steps shown in the foregoing method embodiments.

Electronic devices in embodiments of the present application may include, but are not limited to, mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablets), PMPs (Portable Multimedia Players), vehicle-mounted terminals (such as Mobile terminals such as vehicle navigation terminals), wearable devices, etc., and fixed terminals such as digital TVs, desktop computers, etc.

Embodiments of the present application provide a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the steps and corresponding contents of the foregoing method embodiments can be implemented.

It should be noted that the computer-readable storage medium mentioned above in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination thereof. More specific examples of computer readable storage media may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard drive, random access memory (RAM), read only memory (ROM), removable Programmed read-only memory (EPROM or flash memory), fiber optics, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

As used herein, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer-readable program code is carried. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device . Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wire, optical cable, RF (radio frequency), etc., or any suitable combination of the above.

Computer program code for performing the operations of the present application may be written in one or more programming languages, including, but not limited to, object-oriented programming languages—such as Java, Smalltalk, C++, and Includes conventional procedural programming languages—such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In situations involving remote computers, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as an Internet service provider through Internet connection).

The terms "first", "second", "third", "fourth", "1", "2", etc. (if present) in the description and claims of this application and the above-mentioned drawings are used for Distinguishes similar objects without necessarily describing a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the application described herein can be practiced in other than the order illustrated or described.

It should be understood that although each operation step is indicated by arrows in the flow chart of the embodiment of the present application, the order of implementation of these steps is not limited to the order indicated by the arrows. Unless otherwise specified herein, in some implementation scenarios of the embodiments of the present application, the implementation steps in each flowchart may be executed in other orders according to requirements. In addition, some or all of the steps in each flowchart are based on actual implementation scenarios and may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages may be executed at the same time, and each of these sub-steps or stages may also be executed at different times. In scenarios with different execution times, the execution order of these sub-steps or stages can be flexibly configured according to needs, and the embodiments of the present application do not limit this.

The above are only optional implementation modes of some implementation scenarios of the present application. It should be pointed out that for those of ordinary skill in the technical field, without departing from the technical concept of the solution of the present application, adopting solutions based on the technical ideas of the present application Other similar implementation means also fall within the protection scope of the embodiments of this application.

Claims (10)

1. The non-containerized application management method based on the Kubernetes cluster equipment is characterized by being applied to the Kubernetes cluster equipment;

wherein, kubernetes cluster tool includes: at least one Master Node, at least one Node corresponding to the Master Node;

the Master node further comprises: non-containerized application NCA controller;

the NCA controller includes: an application deployment module and an application management module;

the Node further comprises: the non-containerized application proxy NCAlet component and the non-containerized application;

the method comprises the following steps:

determining, by the application deployment module, an update of deployment resources of the non-containerized application, and updating state resources of the non-containerized application according to the updated deployment resource configuration parameters;

determining, by the application management module, the status resource update, and obtaining updated status resource configuration parameters;

and updating the application state of the non-containerized application according to the updated state resource configuration parameters through the NCAlet component.

2. The Kubernetes cluster-based non-containerized application management method of claim 1, further comprising:

And defining a deployment resource template and a state resource template of the non-containerized application in the Kubernetes cluster equipment in a self-defining resource definition mode.

3. The Kubernetes cluster-based non-containerized application management method of claim 1, further comprising:

and acquiring initial deployment resource configuration parameters through the application deployment module, and updating state resources of the non-containerized application according to the initial deployment resource configuration parameters.

4. A method for managing non-containerized applications based on Kubernetes cluster devices according to any of claims 1-3, wherein determining a deployment resource update of the non-containerized applications specifically comprises:

monitoring the deployment resource configuration parameters of the non-containerized application, and if at least one of deployment resource deletion, deployment resource copy configuration change and deployment resource version change of the deployment resource of the non-containerized application is determined, determining deployment resource update of the non-containerized application.

5. The non-containerized application management method based on Kubernetes cluster equipment of claim 4, wherein the method specifically comprises:

Determining, by the application deployment module, that deployment resources of the non-containerized application undergo a deployment resource deletion change, and correspondingly deleting state resources of the non-containerized application;

determining, by the application management module, that a state resource of the non-containerized application is deleted, and calling an NCAlet component corresponding to the non-containerized application;

and deleting the non-containerized application from the Kubernetes cluster device through the NCAlet component.

6. The non-containerized application management method based on Kubernetes cluster equipment of claim 4, wherein the method specifically comprises:

determining that deployment resources of the non-containerized application undergo deployment resource copy configuration change through the application deployment module, acquiring updated deployment resource copy configuration parameters, and updating state resource copy configuration parameters of the non-containerized application according to the updated deployment resource copy configuration parameters;

determining, by the application management module, the state resource update, and obtaining updated state resource copy configuration parameters;

and deleting and/or adding the corresponding non-containerized application copy according to the updated state resource copy configuration parameters through the NCAlet component.

7. The Kubernetes cluster-based non-containerized application management method of claim 4, further comprising:

determining, by the application deployment module, that deployment resources of the non-containerized application undergo deployment resource version changes, and updating a state resource version of the non-containerized application according to updated deployment resource version configuration parameters;

determining, by the application management module, the state resource update, and obtaining updated state resource version configuration parameters;

and updating the version of the non-containerized application according to the updated state resource version configuration parameters through the NCAlet component.

8. A Kubernetes cluster tool, the Kubernetes cluster tool comprising: at least one Master Node, at least one Node corresponding to the Master Node;

the Master node further comprises: non-containerized application NCA controller;

the NCA controller includes: an application deployment module and an application management module;

the Node further comprises: the non-containerized application proxy NCAlet component and the non-containerized application;

the application deployment module is used for determining the deployment resource update of the non-containerized application and updating the state resource of the non-containerized application according to the updated deployment resource configuration parameters;

The application management module is used for determining the state resource update and acquiring updated state resource configuration parameters;

the NCAlet component is used for updating the application state of the non-containerized application according to the updated state resource configuration parameters.

9. An electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to carry out the steps of the method according to any one of claims 1-7.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any of claims 1-7.