Service grid component management method and device, equipment and storage medium

Abstract

The invention belongs to the technical field of computers, and particularly relates to a service grid component management method and device, equipment and a storage medium. A target CRD object sent by a user is obtained, the target CRD object is analyzed to obtain a plurality of component configuration information sets corresponding to different component types, and according to a preset component configuration rule, whether component configuration information in the component configuration information sets corresponding to the different component types is correct or not is checked in sequence. If the component configuration information in the component configuration information set corresponding to the component type is correct, the component configuration information set corresponding to the component type is distributed to a corresponding component controller according to the component type, and a component corresponding to the component type is deployed, so that the operation condition of the service grid deployment component is detected in real time; according to the method, by automatically configuring the related components of the service grid, the configuration efficiency of the service grid components is improved, and the management accuracy of the service grid components is also improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and in particular to a service mesh component management method and device, equipment and a storage medium. BACKGROUND

[0002] A service mesh is a flexible and configurable infrastructure layer designed for microservice applications, integrating service discovery, load balancing, data encryption, identity verification, authorization, and a variety of functions such as a fuse mechanism. It issues configuration data to each service mesh agent through the control plane to ensure that the agent can correctly proxy service traffic and achieve seamless communication and efficient governance between services. After configuration is complete, further optimization aims to reduce the amount of configuration data pushed to the agent by the control plane and unnecessary pushing to improve pushing efficiency and reduce resource consumption of the agent, thereby optimizing the performance of the entire service mesh.

[0003] In the prior art, the running state of each component of the service mesh is obtained in real time to determine the to-be-modified configuration information of the related components of the service mesh. The operation and maintenance personnel edit a command or a yaml file (i.e., a CRD object) according to the to-be-modified configuration information, and then the operation and maintenance personnel configure the service mesh related components corresponding to the to-be-modified configuration information using the CRD object.

[0004] However, the prior art requires the operation and maintenance personnel to manually configure the service mesh related components, thereby resulting in low efficiency of service mesh configuration optimization. SUMMARY

[0005] The present application provides a service mesh component management method, device, equipment and storage medium to solve the problem of low efficiency of service mesh configuration optimization caused by the need for operation and maintenance personnel to manually configure service mesh related components.

[0006] In a first aspect, the present application provides a service mesh component management method, comprising:

[0007] obtaining a target CRD object sent by a user;

[0008] analyzing the target CRD object to obtain a plurality of component configuration information sets corresponding to different component types;

[0009] According to a preset component configuration rule, sequentially verifying whether the component configuration information in the component configuration information set corresponding to each of the different component types is correct;

[0010] If the component configuration information in the component configuration information set corresponding to the component type is correct, the component configuration information set corresponding to the component type is distributed to the corresponding component controller according to the component type, and the component corresponding to the component type is deployed, so as to detect the running state of the deployed component of the service mesh in real time.

[0011] Optionally, the target CRD object sent by the user comprises:

[0012] receiving a CRD file input by a user through a graphical user interface or a command line interface;

[0013] verifying whether the format and content of the CRD file meet preset specification standards to determine the target CRD object.

[0014] Optionally, the parsing of the target CRD object to obtain a plurality of component configuration information sets respectively corresponding to different component types comprises:

[0015] parsing the target CRD object to determine component configuration information contained in the target CRD object;

[0016] According to the component type, the component configuration information in the target CRD object is classified to obtain a plurality of component configuration information sets respectively corresponding to different component types.

[0017] Optionally, the parsing of the target CRD object to determine component configuration information contained in the target CRD object comprises:

[0018] using a YAML or JSON parser to extract key fields and configuration parameters of each component type according to the Schema definition of the CRD, thereby determining the component configuration information contained in the target CRD object.

[0019] Optionally, the method further comprises:

[0020] If the component configuration information in the component configuration information set corresponding to the component type is incorrect, the incorrect information in the component configuration information set corresponding to the component type is determined according to the preset component configuration rule, and the running state of the corresponding component is updated according to the incorrect information.

[0021] Optionally, the running state of each component of the service mesh comprises a startup state, a running state, a performance index, a log output, and an exception alarm.

[0022] Optionally, the preset component configuration rule comprises a data type, a required item, a mutually exclusive item, and an association relationship between configuration parameters.

[0023] In a second aspect, the present application provides a service mesh component management device, comprising:

[0024] an acquisition module configured to acquire a target CRD object sent by a user;

[0025] a processing module, configured to perform parsing processing on the target CRD object to obtain a plurality of component configuration information sets respectively corresponding to different component types;

[0026] a checking module, configured to sequentially check, according to a preset component configuration rule, whether the component configuration information in the component configuration information set corresponding to each of the different component types is correct;

[0027] The processing module is configured to, if the component configuration information in the component configuration information set corresponding to the component type is correct, distribute the component configuration information set corresponding to the component type to a corresponding component controller according to the component type, and deploy a component corresponding to the component type, so as to detect the running state of the service mesh in real time.

[0028] Optionally, the service mesh component management apparatus further includes a receiving module and a verifying module.

[0029] The receiving module is configured to receive a CRD file input by a user through a graphical user interface or a command line interface.

[0030] The verifying module is configured to verify whether the format and content of the CRD file conform to a preset specification standard, to determine the target CRD object.

[0031] Optionally, the processing module is further configured to perform parsing on the target CRD object to determine the component configuration information contained in the target CRD object.

[0032] The processing module is further configured to classify the component configuration information in the target CRD object according to component types, to obtain a plurality of component configuration information sets respectively corresponding to different component types.

[0033] Optionally, the service mesh component management apparatus further includes a determining module.

[0034] The determining module is configured to use a YAML or JSON parser to extract key fields and configuration parameters of each component type according to a Schema definition of the CRD, to determine the component configuration information contained in the target CRD object.

[0035] Optionally, the determining module is further configured to, if the component configuration information in the component configuration information set corresponding to the component type is incorrect, determine incorrect information in the component configuration information set corresponding to the component type according to a preset component configuration rule, and update the running state of the corresponding component according to the incorrect information.

[0036] In a third aspect, the present application provides a service mesh component management device, including:

[0037] a memory;

[0038] a processor;

[0039] The memory stores computer-executable instructions.

[0040] The processor executes the computer-executable instructions stored in the memory to implement the service mesh component management method as described above in the first aspect and various possible implementations of the first aspect.

[0041] In a fourth aspect, the present application provides a computer storage medium, wherein the computer storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the service mesh component management method as described in the first aspect and various possible implementations of the first aspect.

[0042] The service mesh component management method provided by the present application obtains a target CRD object sent by a user, performs analysis processing on the target CRD object, obtains a plurality of component configuration information sets respectively corresponding to different component types, according to a preset component configuration rule, sequentially verifies whether the component configuration information in the component configuration information set corresponding to each component type is correct, if the component configuration information in the component configuration information set corresponding to each component type is correct, according to the component type, distributes the component configuration information set corresponding to the component type to a corresponding component controller, and deploys a component corresponding to the component type, so as to detect the running state of the service mesh deployment component in real time. The method automatically configures the service mesh related components, improves the service mesh component configuration efficiency, and improves the service mesh component management accuracy. BRIEF DESCRIPTION OF DRAWINGS

[0043] The accompanying drawings, which are incorporated into and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application.

[0044] Figure 1 Flowchart of the service mesh component management method provided by the present application Figure 1 ;

[0045] Figure 2 Flowchart of the service mesh component management method provided by the present application Figure 2 ;

[0046] Figure 3 Structural schematic diagram of the service mesh component management device provided by the present application;

[0047] Figure 4 Structural schematic diagram of the service mesh component management device provided by the present application.

[0048] The specific embodiments of the application have been shown by way of example in the above figures, and will be described in greater detail below. These figures and this written description are not intended to limit the scope of the inventive concept in any way, but rather to illustrate the inventive concept to one of ordinary skill in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0049] Exemplary embodiments will be described in detail with reference to the drawings, of which examples are shown. Unless otherwise noted, the same numbers on different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the application as detailed in the appended claims.

[0050] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards, and provide corresponding operation portal for user to choose authorization or refusal.

[0051] As the cornerstone of microservice architecture, service mesh builds a highly flexible and configurable middle layer, tailored for modern distributed applications. It not only integrates core functions such as service discovery and load balancing, but also strengthens security and management capabilities such as data encryption, identity verification, authorization, and circuit breaking protection. This layer, through an intelligent control plane, precisely issues configuration instructions to grid agents distributed across service nodes, ensuring smooth and secure communication between services and providing strong support for microservice architecture governance.

[0052] In the prior art, the configuration management of the service mesh relies on real-time monitoring of the running state of each component to identify and determine the configuration information that needs to be adjusted. Subsequently, the operation and maintenance personnel need to manually edit the corresponding commands or yaml files (as CRD objects) according to these to-be-modified configuration information, and finally configure the related components of the service mesh through these CRD objects.

[0053] However, the configuration optimization of the service mesh in the prior art is limited to manual operation by the operation and maintenance personnel, and this dependence not only increases the risk of human error, but also greatly reduces the speed and efficiency of configuration updates, thereby restricting the optimization of the overall performance of the service mesh.

[0054] To solve the above problems, the application provides a service mesh component management method, which directly analyzes the target CRD object submitted by the user, decomposes the target CRD object into a plurality of configuration information sets for different component types. Subsequently, the preset component configuration rule is used to realize the automatic verification of the component configuration information. Once the verification is passed, the correct configuration information is distributed to the corresponding component controller, and the instant deployment and operation of the component are realized. This method not only significantly improves the configuration efficiency of the service mesh component, but also greatly enhances the accuracy and reliability of the service mesh component deployment through automatic management, realizes the real-time detection and optimization of the running state of the service mesh deployment component.

[0055] The technical solutions of the application and how the technical solutions solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the application will be described below with reference to the drawings.

[0056] Figure 1 Flow of the service mesh component management method provided by the application Figure 1 As shown in Figure 1 , the service mesh component management method shown in the embodiment includes:

[0057] S101: Obtain a target CRD object sent by a user.

[0058] The target CRD object includes the resource type, name and namespace of the CRD instance.

[0059] Obtaining the target CRD object sent by the user means receiving and identifying the instance of the custom resource definition (i.e., the target CRD object) specified by the user in some way (such as kubectl command, API request, user interface operation, etc.) in the Kubernetes environment. The target CRD object is created according to the CRD definition and is used to store and manage application-specific configurations, states or other data. Obtaining the target CRD object means retrieving the specific custom resource instance that the user wants to operate or query from the Kubernetes cluster.

[0060] The reason why the target CRD object sent by the user is important is that it allows the user to interact with the custom resources in the Kubernetes cluster. These custom resources may represent application configurations, database migrations, service level agreement (SLA) definitions, and other critical information. By obtaining the target CRD object, the user can query its current state, update the configuration, trigger operations, or perform other management tasks.

[0061] First, the resource type, name, and namespace of the CRD instance to be obtained (i.e., the target CRD object) are obtained. These pieces of information are usually provided through user input, API request parameters, or user interface selections.

[0062] According to user needs, a suitable method is selected to obtain the target CRD object. For example, using the kubectl command-line tool, the kubectl get command with appropriate parameters can be used to query the target CRD object; if a client program is written, the Kubernetes API client library can be used to send HTTP requests and parse responses, build request URLs, set request headers, send requests, and handle responses.

[0063] S102: The target CRD object is parsed and processed to obtain a plurality of component configuration information sets corresponding to different component types.

[0064] Parsing and processing the target CRD object means decoding, analyzing, and extracting the content of the user-submitted or specified custom resource definition (i.e., the target CRD object). During this process, the service mesh management controller system identifies the data structures in the target CRD object, especially those associated with different component types, and classifies them into different component configuration information sets. Each set contains all the configuration parameters and settings required for a specific component type, so that it can be accurately applied to the corresponding component later.

[0065] First, the target CRD object is used to store complex application configurations, which involve multiple different components, each with its unique configuration requirements. By parsing and processing, these configuration information can be clearly separated for easy management and maintenance. Second, organizing configuration information into component configuration information sets can simplify the initialization and configuration process of components, making deployment and updating of applications more efficient and accurate. Finally, parsing and processing the target CRD object to obtain a plurality of component configuration information sets corresponding to different component types promotes the decoupling and reuse of components, allowing them to be flexibly combined and configured in different applications or environments.

[0066] S103: According to the preset component configuration rules, the component configuration information in the component configuration information sets corresponding to different component types is sequentially verified for correctness.

[0067] The preset component configuration rules include requirements for data types, value ranges, mandatory items, and dependency relationships of configuration items.

[0068] Before deploying or updating components, the service mesh management controller system checks each configuration item in the component configuration information set according to a set of predefined rules or standards to ensure that they meet the expected format, range, dependency, and other requirements. This verification process ensures the stable operation of components and avoids configuration errors.

[0069] Firstly, verifying the correctness of component configuration information in the component configuration information set corresponding to multiple different component types can help to detect and correct configuration errors in advance, avoiding failures during component operation. By solving problems in the verification stage, the reliability and stability of components can be significantly improved. Secondly, the verification process can ensure that all components are configured according to uniform standards. In addition, as the complexity and size of components continue to increase, the number of configuration information will also increase dramatically. Through automated verification tools, work efficiency can be greatly improved, and human errors can be reduced.

[0070] According to the preset component configuration rules, the corresponding verification logic is written. This can be achieved through scripts, program codes, or specialized verification tools. The verification logic should be able to traverse each component configuration information set and check each configuration item one by one, and give the verification result.

[0071] Finally, execute the verification logic and process according to the verification result. If all configuration items pass the verification, the deployment or update process of the component can continue. If it is found that some configuration items do not pass the verification, specific error prompts should be given according to the verification result, and users or automated processes should be guided to correct them. After correction, the verification process can be executed again until all configuration items meet the requirements.

[0072] S104: If the component configuration information in the component configuration information set corresponding to the component type is correct, distribute the component configuration information set corresponding to the component type to the corresponding component controller according to the component type, and deploy the component corresponding to the component type, thereby detecting the running status of the service mesh deployed component in real time.

[0073] Firstly, by distributing the configuration information set to the corresponding component controller, it can ensure that each component can receive correct configuration information and initialize itself according to these information, thereby achieving the expected function and performance. Secondly, real-time detection of the running status of the service mesh deployed component is crucial for timely detection and solution of problems. By monitoring the running status of the component, abnormal situations can be quickly responded to, reducing the risk of service interruption. In addition, this distribution and deployment mechanism also supports dynamic expansion and contraction of services, improving the flexibility and scalability of the service mesh.

[0074] First, the set of validated component configuration information is distributed to the corresponding component controllers based on the component type. This involves interacting with the communication interface of the component controller and sending the configuration information in the appropriate format to the controller.

[0075] Upon receiving the configuration information, the component controller deploys or updates the corresponding component based on the information. During deployment, the controller ensures that the component's dependencies are met and that interactions with other components are as expected.

[0076] After deployment, the service mesh management system needs to monitor the running status of each component in the service mesh in real time. This can be achieved by integrating monitoring and log collection tools that can collect performance metrics, error logs, and other information from components and analyze and display them. Through real-time monitoring, potential problems can be discovered and resolved in a timely manner, ensuring the stable operation of the service mesh.

[0077] The service mesh component management method provided in this embodiment includes the following steps:

[0078] Figure 2 The flow of the service mesh component management method provided in this application Figure 2 As shown in Figure 1 , this embodiment is based on the Figure 3 embodiment and provides a detailed description of the service mesh component management method. The service mesh component management method shown in this embodiment includes the following steps:

[0079] S201: Receive the CRD file input by the user through the graphical user interface or command line interface.

[0080] Receiving a CRD file input by a user through a graphical user interface (GUI) or a command line interface (CLI) refers to a mechanism provided by a service mesh management system that allows users to input or upload a custom resource definition (CRD) file in the form of a file through a graphical user interface or a text command line. A CRD file is a YAML or JSON file used in Kubernetes to define new custom resource types, which extends the functionality of the Kubernetes API and allows users to define and manage resources that do not belong to the core API of Kubernetes.

[0081] Firstly, the service mesh management system enables users to flexibly define and manage their own application resources, rather than relying solely on the resources provided by the Kubernetes core API. Secondly, the graphical user interface (GUI) or command line interface (CLI) serves as the main way for users to interact with the service mesh management system, providing an intuitive and convenient operation interface, reducing the learning cost and operation difficulty of users. Finally, by receiving the CRD file, the service mesh management system can automatically parse and process these files, deploying user-defined resources to the Kubernetes cluster, achieving rapid configuration and dynamic management of resources.

[0082] S202: Verify whether the format and content of the CRD file meet the preset specification standard to determine the target CRD object.

[0083] After the service mesh management system receives the CRD file submitted by the user, a series of checking and comparison operations are performed to ensure that the CRD file meets the pre-defined standards and requirements in terms of syntax, structure, fields, etc. This process aims to filter out valid CRD files and avoid problems caused by format or content errors, so as to ensure that the file can be correctly parsed and processed later to generate the target CRD object.

[0084] Firstly, as a key file for defining custom resources in Kubernetes, the correctness of the format and content of the CRD file directly affects the management and use of subsequent resources. If the CRD file has errors, it may cause problems such as incorrect resource deployment, missing or inconsistent configuration information, and thus affect the stability and reliability of the entire service mesh management system. Secondly, the preset specification standard serves as a guide and constraint for the writing of CRD files, helping to unify the writing style of files, reduce the probability of errors, and improve the readability and maintainability of code. Finally, by verifying the compliance of the CRD file, problems can be found and solved in the early stage, avoiding greater impact and loss in the subsequent development and deployment process.

[0085] S203: Analyze the target CRD object to determine the component configuration information contained therein.

[0086] Analyzing the target CRD object to determine the component configuration information contained therein involves in-depth analysis of the target CRD object that has been verified to comply with the preset specification standards. By reading its data structure, field values, and other information, the content related to component configuration is identified and extracted. This process is an understanding of the custom resource structure defined within the CRD file and an accurate grasp of the meaning of its fields, aiming to convert the abstract description in the CRD object into specific component configuration information, providing basic data for subsequent component deployment and management.

[0087] The target CRD object, as a user-defined custom resource, contains detailed configuration information about components within it. These information is crucial for the correct deployment, operation, and management of components. By analyzing the target CRD object, the service mesh management system can understand the specific configuration requirements of the components, including their dependency relationships, resource limitations, environment variables, etc., so that it can create and manage component instances according to the expected configuration requirements. In addition, analyzing the target CRD object helps to realize the dynamic and flexible configuration of components, supporting configuration changes and updates at runtime as needed.

[0088] Optionally, the specific implementation of the method is as follows: using a YAML or JSON parser, according to the Schema definition of CRD, extracting the key fields and configuration parameters of each component type, thereby determining the component configuration information contained in the target CRD object.

[0089] Using a YAML or JSON parser, according to the Schema definition of CRD, extracting the key fields and configuration parameters of each component type, is a method of automatically processing and analyzing custom resource objects in the Kubernetes environment. CRD allows users to extend the Kubernetes API to accommodate their specific application-level abstractions. This method uses a parser to parse the YAML or JSON format configuration file of the CRD object, and by understanding its Schema structure, it can accurately identify and extract the key information and configuration details of each component that constitutes the CRD.

[0090] Firstly, the service mesh management system improves the flexibility and scalability of Kubernetes cluster management, allowing developers and administrators to customize resources and manage their configurations according to business needs. Secondly, automatically parsing and extracting key information from CRD objects can simplify configuration management and version control processes, reducing human error. Finally, by programmatically processing CRD configurations, it is easier to implement configuration information verification, conversion, and synchronization, supporting complex deployment and operation scenarios such as multi-environment deployment, configuration drift detection, etc.

[0091] S204: According to the component type, the component configuration information in the target CRD object is classified to obtain a plurality of component configuration information sets respectively corresponding to different component types.

[0092] Further processing of the component configuration information in the parsed target CRD object, according to the specific type of the component, divides it into different sets. This process is similar to grouping or classifying a set of data, but here the basis for classification is the type of component, and the purpose is to organize related configuration information together to facilitate subsequent management and operation for different component types.

[0093] First, different component types may have different configuration requirements and attributes, and processing their configuration information separately can ensure that each component receives the correct configuration and avoid problems caused by configuration errors. Secondly, the classified component configuration information set allows the service mesh management system to more efficiently manage and maintain component configurations. In addition, classification helps improve the scalability and flexibility of the service mesh management system. When a new component type needs to be added, only the corresponding processing needs to be added to the classification logic, without the need for large-scale modifications to the entire service mesh management system.

[0094] S205: According to the preset component configuration rules, sequentially verify whether the component configuration information in the component configuration information set corresponding to the plurality of different component types is correct, if yes, execute step S206; if not, execute step S207.

[0095] After having multiple component configuration information sets classified by component type, the service mesh management system will check each set of component configuration information according to a series of predefined configuration rules. This process aims to ensure that all component configurations are valid and meet expectations, thereby avoiding problems caused by configuration errors during component deployment or operation.

[0096] The reason for performing such a check operation is as follows: first, the correctness of the component configuration directly affects the stability and reliability of the entire system. If there is an error in the configuration of a component, it may cause the component to malfunction, even affecting the operation of other components or the entire system. Second, by checking against preset component configuration rules, it can ensure that all components follow uniform configuration standards and specifications, which is beneficial for system maintenance and upgrading. In addition, the checking process can help developers or operators to discover and correct configuration errors in a timely manner, avoiding greater impact and loss in subsequent development and deployment processes.

[0097] According to the preset component configuration rules, the component configuration information in the component configuration information set corresponding to each component type is checked in turn. If the component configuration information is correct, the component configuration information set corresponding to the component type is distributed to the corresponding component controller according to the component type, and the component corresponding to the component type is deployed, so as to detect the running state of the service mesh in real time. If the component configuration information is not correct, the error information in the component configuration information set corresponding to the component type is determined according to the preset component configuration rules, and the running state of the corresponding component is updated according to the error information.

[0098] S206: According to the component type, the component configuration information set corresponding to the component type is distributed to the corresponding component controller, and the component corresponding to the component type is deployed, so as to detect the running state of the service mesh in real time.

[0099] Based on the specific type of the component and its corresponding configuration information, precise deployment operations are performed. This process first identifies and classifies component configuration information, then passes these information to respective component controllers, which start and configure components according to these information. Once the components are deployed, the service mesh management control system detects in real time to determine the running state of these components in the service mesh, ensuring they work as expected and meet service requirements.

[0100] By distributing configuration information by component type and deploying independently, the service mesh management control system can more efficiently manage complex microservice architectures. In addition, real-time detection of component running state is crucial for quickly identifying and resolving potential problems, helping to maintain the stability and reliability of the service mesh. In addition, this component-based deployment and monitoring method also supports dynamic updates and configuration changes, enabling the service mesh to adapt to changing business needs and technical environments.

[0101] Among them, the running state of each component of the service mesh includes: startup state, running state, performance index, log output and exception alarm.

[0102] The running status of the service mesh covers multiple key aspects of its core components, including their startup state (to ensure that the components have been properly started and are running), running state (to determine the stability and performance of the components through health checks and resource detection), performance indicators (such as throughput, latency, and error rate, to measure the performance efficiency of the components), log output (to record detailed running logs for tracking and diagnosing problems), and exception alerts (to automatically notify when an exception or threshold is detected, to enable rapid response and problem resolution).

[0103] S207: Determine the error information in the component configuration information set corresponding to the component type according to the preset component configuration rule, and update the running state of the corresponding component according to the error information.

[0104] The service mesh management system checks the configuration information of each component through a series of predefined rules. These rules aim to ensure that each component is configured in the expected way, thereby avoiding performance problems or failures caused by configuration errors. When the service mesh management system detects that the configuration information of a component does not comply with the preset rules, it identifies the specific error information and automatically adjusts or notifies the user to update the running state of the component accordingly, to ensure the overall stability and reliability of the system.

[0105] Firstly, automated configuration verification and error handling can significantly improve the maintainability and reliability of the system, reducing problems caused by human configuration errors. Secondly, by managing component configuration through preset rules, it can ensure that all components follow uniform standards, helping to improve the overall performance and security of the service mesh management system. Finally, updating the running state of the component in a timely manner according to the error information can quickly respond to potential problems, avoid problem expansion, and also provide convenience for troubleshooting of the service mesh management system.

[0106] Among them, the preset component configuration rules include: data type, mandatory items, mutually exclusive items, and the association relationship between configuration parameters.

[0107] The service mesh component management method provided by the embodiment comprises the following steps: a CRD file input by a user through a graphical user interface or a command line interface is received, the format and content of the CRD file are verified to determine whether the format and content of the CRD file conform to preset specification standards, a target CRD object is determined, the target CRD object is parsed, component configuration information contained in the target CRD object is determined, the component configuration information in the target CRD object is classified according to component types, a plurality of component configuration information sets respectively corresponding to different component types are obtained, component configuration information in the component configuration information sets corresponding to different component types is sequentially verified according to preset component configuration rules, if the component configuration information is correct, the component configuration information set corresponding to a component type is distributed to a corresponding component controller according to the component type, and a component corresponding to the component type is deployed, so that the running condition of a service mesh deployment component is detected in real time, and if the component configuration information is incorrect, error information in the component configuration information set corresponding to the component type is determined according to the preset component configuration rules, and the running state of the corresponding component is updated according to the error information. The method improves the service mesh component configuration efficiency and improves the service mesh component management accuracy by automatically configuring service mesh related components.

[0108] Figure 3 The structure diagram of the service mesh component management device provided by the present application is shown in the figure. Figure 4 As shown in the figure, the service mesh component management device 300 provided by the embodiment comprises:

[0109] The acquisition module 301 is configured to acquire a target CRD object sent by a user.

[0110] The processing module 302 is configured to parse the target CRD object to obtain a plurality of component configuration information sets respectively corresponding to different component types.

[0111] The verification module 303 is configured to sequentially verify the component configuration information in the component configuration information sets corresponding to different component types according to preset component configuration rules.

[0112] The processing module 302 is configured to, if the component configuration information in the component configuration information set corresponding to a component type is correct, distribute the component configuration information set corresponding to the component type to a corresponding component controller according to the component type, and deploy a component corresponding to the component type, so as to detect the running condition of a service mesh deployment component in real time.

[0113] Optionally, the service mesh component management device further comprises a receiving module 304 and a verification module 305.

[0114] The receiving module 304 is configured to receive a CRD file input by a user through a graphical user interface or a command line interface.

[0115] The verification module 305 is configured to verify whether the format and content of the CRD file conform to preset specification standards to determine a target CRD object.

[0116] Optionally, the processing module 302 is further configured to parse the target CRD object to determine component configuration information contained in the target CRD object.

[0117] The processing module 302 is further configured to classify the component configuration information in the target CRD object according to component types to obtain a plurality of component configuration information sets respectively corresponding to different component types.

[0118] Optionally, the service mesh component management apparatus further includes a determination module 306.

[0119] The determination module 306 is configured to use a YAML or JSON parser to extract key fields and configuration parameters of each component type according to a Schema definition of a CRD, so as to determine the component configuration information contained in the target CRD object.

[0120] Optionally, the determination module 306 is further configured to, if the component configuration information in the component configuration information set corresponding to a component type is incorrect, determine incorrect information in the component configuration information set corresponding to the component type according to preset component configuration rules, and update a running state of the corresponding component according to the incorrect information.

[0121] Figure 4 A structural schematic diagram of a service mesh component management device provided by the present application is shown in FIG. 4. ​ As shown in FIG. 4, the present application provides a service mesh component management device 400, which includes a receiver 401, a transmitter 402, a processor 403, and a memory 404.

[0122] The receiver 401 is configured to receive instructions and data.

[0123] The transmitter 402 is configured to transmit instructions and data.

[0124] The memory 404 is configured to store computer execution instructions.

[0125] The processor 403 is configured to execute the computer execution instructions stored in the memory 404 to implement each step performed by the service mesh component management method in the above-described embodiments. For details, refer to the related description in the foregoing service mesh component management method embodiments.

[0126] Optionally, the memory 404 can be independent or integrated with the processor 403.

[0127] When the memory 404 is independently provided, the electronic device further includes a bus for connecting the memory 404 and the processor 403.

[0128] The application further provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions. When the processor executes the computer execution instructions, the service mesh component management method performed by the service mesh component management device is implemented.

[0129] It should be noted that, for the foregoing method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the application is not limited to the action order described, because according to the application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the application.

[0130] It should be further noted that, although each step in the flowchart is displayed in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise stated in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed in rotation or alternation with other steps or sub-steps or stages of other steps.

[0131] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the application can also be realized by other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and actual implementation can have another division way. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0132] In addition, unless otherwise specified, each functional unit / module in each embodiment of the application can be integrated in one unit / module, or each unit / module can exist physically, or two or more units / modules can be integrated together. The integrated unit / module can be realized in the form of hardware or in the form of software program module.

[0133] If the integrated units / modules are implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the storage unit can be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0134] If the integrated units / modules are implemented in the form of software program modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the essential part or all or part of the technical solutions that make contributions to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0135] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combination of the technical features does not exist contradictory, it should be considered as the scope of the present application

[0136] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0137] It is to be understood that the application is not limited to the precise construction herein disclosed and shown in the drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is limited only by the claims that follow.

Claims

1. A service mesh component management method, characterized by, The method comprises: obtaining a target CRD object sent by a user; parsing the target CRD object to obtain a plurality of component configuration information sets respectively corresponding to different component types; according to a preset component configuration rule, sequentially checking whether the component configuration information in the component configuration information sets corresponding to the plurality of different component types is correct; if the component configuration information in the component configuration information set corresponding to the component type is correct, distributing the component configuration information set corresponding to the component type to a corresponding component controller according to the component type, and deploying the component corresponding to the component type, so as to detect the running state of the service mesh in real time.

2. The method of claim 1, wherein, The method comprises: receiving a CRD file input by a user through a graphical user interface or a command line interface; verifying whether the format and content of the CRD file meet the preset specification standard to determine the target CRD object.

3. The method of claim 1, wherein, The method comprises: parsing the target CRD object to determine the component configuration information contained in the target CRD object; classifying the component configuration information in the target CRD object according to the component type to obtain a plurality of component configuration information sets respectively corresponding to different component types.

4. The method of claim 3, wherein, The method comprises: using a YAML or JSON parser to extract the key fields and configuration parameters of each component type according to the Schema definition of the CRD, so as to determine the component configuration information contained in the target CRD object.

5. The method of claim 1, wherein, The method further comprises: if the component configuration information in the component configuration information set corresponding to the component type is incorrect, determining the error information in the component configuration information set corresponding to the component type according to the preset component configuration rule, and updating the running state of the corresponding component according to the error information.

6. The method according to claims 1-5, characterized in that, The running state of each component of the service mesh comprises a starting state, a running state, a performance index, a log output and an exception alarm.

7. The method according to any one of claims 1 to 5, characterized in that, The preset component configuration rule comprises a data type, a mandatory item, a mutual exclusion item and an association relationship between configuration parameters.

8. A service mesh component management apparatus, characterized by, The method comprises: an obtaining module configured to obtain a target CRD object sent by a user; a processing module configured to parse the target CRD object to obtain a plurality of component configuration information sets respectively corresponding to different component types; the processing module is further configured to sequentially check whether the component configuration information in the component configuration information sets corresponding to the plurality of different component types is correct according to a preset component configuration rule; the processing module is further configured to, if the component configuration information in the component configuration information set corresponding to the component type is correct, distribute the component configuration information set corresponding to the component type to a corresponding component controller according to the component type, and deploy the component corresponding to the component type, so as to detect the running state of the service mesh in real time.

9. A service mesh component management device, characterized by, The method comprises: a processor, and a memory connected with the processor in communication; the memory stores computer execution instructions; The processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, implement the method of any one of claims 1-7.

Images