Container arrangement engine configuration verification method and device, equipment and storage medium

Through comprehensive and systematic configuration verification of the Kubernetes container orchestration engine, the problem of high configuration error rate is solved, the accuracy and security of configuration are achieved, and the high availability and business continuity of the network security competition is ensured.

CN118963775AInactive Publication Date: 2024-11-15JIANGSU BOZHI SOFTWARE TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410973751.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-15
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In the network security competition, traditional master-secure switching technology is difficult to ensure the accurate configuration of the Kubernetes container orchestration engine, resulting in a high configuration error rate, affecting the high availability of services and business continuity.

Method used

Provide a container orchestration engine configuration verification method, which generates a verification report and determines the configuration items to be adjusted based on the report by verifying items such as maintaining an active service connection environment, deployment configuration, service configuration, storage configuration and security verification, and performs a verification report. Configuration adjustments to ensure configuration accuracy and security.

Benefits of technology

It significantly reduces the configuration error rate, improves deployment reliability and security defense levels in network security competitions, ensures early detection and immediate correction of configuration problems, and improves operation and maintenance efficiency and overall system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118963775A_ABST
    Figure CN118963775A_ABST
Patent Text Reader

Abstract

The invention discloses a container arrangement engine configuration verification method and device, equipment and a storage medium. The method is applied to a network security competition scene, and comprises the following steps: verifying a to-be-tested container arrangement engine in sequence according to each verification item to generate a verification result; generating a verification report according to each verification result, and determining a to-be-adjusted configuration item according to the verification report; and performing configuration adjustment on the to-be-tested container arrangement engine through the to-be-adjusted configuration item. Various configurations are comprehensively and systematically verified before the container orchestration engine cluster is deployed, the correctness, high efficiency and safety of the configurations are ensured, verification items comprise service connection maintaining active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and safety verification, the configuration accuracy is improved, and the configuration efficiency is improved. And the verification efficiency is obviously improved, and early discovery and immediate correction of the configuration problem are ensured. The operation and maintenance efficiency and the overall performance of the system are further improved by adjusting the configuration of the configuration item to be adjusted.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of network security technology, and in particular to a container orchestration engine configuration verification method, device, equipment and storage medium. Background Art

[0002] As network security becomes increasingly important in the digital age, the need for continuous and stable system operation becomes increasingly stringent, especially for high-intensity network security competitions. Traditional active-standby switching technology is unable to handle high concurrent traffic and ensure high service availability. Therefore, the industry is gradually inclined to adopt Kubernetes, an advanced container orchestration solution. With its excellent cluster management and automatic expansion capabilities, Kubernetes provides strong support for the competition environment and ensures uninterrupted service.

[0003] As the master of container orchestration technology, Kubernetes not only plans complex deployment architectures and network policies through YAML configuration files, but also implements dynamic load balancing, efficient resource configuration management, and comprehensive security policies. However, due to the richness and complexity of configurations, how to ensure accurate configuration and follow best practices has become a major challenge for the operation and maintenance team.

[0004] In past practices, enterprises have relied on manual review of configurations or analysis of logs after service startup to discover configuration errors, but both methods have their own disadvantages: manual review is not only time-consuming, but also easily affected by human factors, resulting in omissions of details; and relying on runtime log troubleshooting means that problems are discovered with a delay, which not only wastes resources, but may also cause service interruptions, seriously threatening business continuity. Summary of the invention

[0005] The present invention provides a container orchestration engine configuration verification method, device, equipment and storage medium to reduce the configuration error rate and improve deployment reliability, thereby improving the security defense level of network security competitions, preventing unauthorized access and data leakage, and building a solid line of defense for network security competitions.

[0006] According to one aspect of the present invention, a container orchestration engine configuration verification method is provided, which is applied to a network security competition scenario. The method includes:

[0007] Verify the container orchestration engine to be tested in turn according to each verification item to generate verification results, where the verification items include maintaining active service connection environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification;

[0008] Generate a verification report based on each verification result, and determine the configuration items to be adjusted based on the verification report;

[0009] Adjust the configuration of the container orchestration engine to be tested through the configuration items to be adjusted.

[0010] Optionally, when the verification item is to verify the configuration of maintaining an active service connection environment, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: calling a preset command to perform a connectivity test on the container orchestration engine to be tested to generate a connectivity test result, wherein the connectivity test result includes physical address connectivity and virtual address connectivity; parsing the configuration protocol to generate a parsing protocol, and verifying the configuration of the election policy based on the parsing protocol to generate a policy detection result; and using the connectivity test result and the policy detection result as the verification result corresponding to the configuration verification of maintaining an active service connection environment.

[0011] Optionally, when the verification project is deployment configuration verification, the container orchestration engine to be tested is verified in turn according to each verification project to generate a verification result, including: taking each preset deployment configuration verification sub-project as a target verification sub-project in turn, wherein the deployment configuration verification sub-project includes version consistency verification, label uniqueness verification, name uniqueness verification, namespace consistency verification, replica quantity verification, template label integrity verification and image validity and pull strategy verification; traversing the deployment configuration of the container orchestration engine to be tested according to the target verification sub-project to determine each target field; obtaining the standard value corresponding to each target field, and determining the verification result corresponding to the deployment configuration verification according to the standard value and the target field.

[0012] Optionally, when the verification item is service configuration verification, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: verifying the service configuration of the container to be tested according to preset service configuration verification sub-items to generate a verification result corresponding to the service configuration verification, wherein the service configuration verification sub-items include metadata consistency verification, port configuration consistency verification, internal port alignment verification, service type standardization verification and session affinity verification.

[0013] Optionally, when the verification item is storage configuration verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: verifying the storage configuration of the container to be tested according to preset storage configuration verification sub-items to generate a verification result corresponding to the storage configuration verification, wherein the storage configuration verification sub-items include whether to perform mandatory verification of dynamic configuration management, configuration file format legality verification and character encoding standardization verification.

[0014] Optionally, when the verification item is a security verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: calling a preset verification script to determine the security policy startup status and network policy configuration status of the container orchestration engine to be tested; determining the sensitive information status of the configuration of the container orchestration engine to be tested according to the sensitive data list, wherein the sensitive data list includes database passwords and keys; and taking the security policy startup status, network policy configuration status and sensitive information status as the verification results corresponding to the security verification.

[0015] Optionally, a verification report is generated based on each verification result, and the configuration items to be adjusted are determined based on the verification report, including: determining the target verification item corresponding to each verification result; obtaining a verification report template, and determining the target position corresponding to the target verification item in the verification report template; combining the corresponding verification results and the verification report template according to the target position to generate a verification report; determining whether there are abnormal items in the verification report, and if so, treating the abnormal items as configuration items to be adjusted; otherwise, determining that there are no configuration items to be adjusted.

[0016] According to another aspect of the present invention, a container orchestration engine configuration verification device is provided, the device comprising:

[0017] A verification result generation module is used to verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining service connection active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification;

[0018] A module for determining configuration items to be adjusted, used to generate a verification report according to each of the verification results, and determine the configuration items to be adjusted according to the verification report;

[0019] A configuration adjustment module is used to adjust the configuration of the container orchestration engine to be tested through the configuration item to be adjusted.

[0020] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0021] at least one processor; and

[0022] a memory communicatively connected to the at least one processor; wherein,

[0023] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a container orchestration engine configuration verification method described in any embodiment of the present invention.

[0024] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a container orchestration engine configuration verification method described in any embodiment of the present invention when executed.

[0025] The technical solution of the embodiment of the present invention ensures the correctness, efficiency and security of the configuration by comprehensively and systematically verifying various configurations before the container orchestration engine cluster is deployed. The verification items include maintaining the active environment configuration verification of service connections, deployment configuration verification, service configuration verification, storage configuration verification and security verification, which improves the accuracy of the configuration and significantly improves the verification efficiency, ensuring the early discovery and immediate correction of configuration problems. By adjusting the configuration of the configuration items to be adjusted, the operation and maintenance efficiency and the overall performance of the system are further improved.

[0026] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0028] Figure 1 This is a flowchart of a container orchestration engine configuration verification method provided according to Embodiment 1 of the present invention;

[0029] Figure 2 It is a schematic diagram of a configuration verification process for maintaining an active service connection environment according to Embodiment 1 of the present invention;

[0030] Figure 3 is a schematic diagram of a deployment configuration verification process provided according to Embodiment 1 of the present invention;

[0031] Figure 4 is a schematic diagram of a service configuration verification process provided according to Embodiment 1 of the present invention;

[0032] Figure 5 is a schematic diagram of a storage configuration verification process provided according to Embodiment 1 of the present invention;

[0033] Figure 6 is a schematic diagram of a security verification process provided according to Embodiment 1 of the present invention;

[0034] Figure 7 is a flowchart of another method for verifying configuration of a container orchestration engine provided according to Embodiment 2 of the present invention;

[0035] Figure 8 This is a schematic diagram of a verification report provided according to Embodiment 2 of the present invention;

[0036] Fig. 9 2 is a schematic diagram of the structure of a container orchestration engine configuration verification device provided according to Embodiment 3 of the present invention;

[0037] Fig.10 It is a structural schematic diagram of an electronic device for implementing a container orchestration engine configuration verification method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0039] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0040] Embodiment 1

[0041] Figure 1 A flowchart of a method for verifying the configuration of a container orchestration engine is provided for the first embodiment of the present invention. This embodiment is applicable to network security competition scenarios. The method can be executed by a container orchestration engine configuration verification device. The container orchestration engine configuration verification device can be implemented in the form of hardware and / or software. The container orchestration engine configuration verification device can be configured in a computer controller. Figure 1 As shown, the method includes:

[0042] S110. Verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining service connection active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification.

[0043] Among them, the container orchestration engine to be tested refers to Kubernetes, abbreviated as K8s, which is an open source container orchestration platform for automated deployment, expansion and management of containerized applications.

[0044] Specifically, the environment configuration verification for maintaining active service connections refers to the keepAlive environment verification, which is to maintain the environment configuration for active service connections to ensure that the service is not disconnected due to long periods of no requests. Deployment configuration verification refers to Deployment configuration verification, which is used to manage the life cycle of Pod creation, update, and replication. Service configuration verification refers to Service configuration verification. Service configuration defines how to access services within the Kubernetes cluster, including load balancing, access portals, etc. Storage configuration verification refers to ConfigMap, which is a Kubernetes object used to store configuration data, making it possible to separate application configuration and code.

[0045] Optionally, when the verification item is to verify the configuration of maintaining an active service connection environment, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: calling a preset command to perform a connectivity test on the container orchestration engine to be tested to generate a connectivity test result, wherein the connectivity test result includes physical address connectivity and virtual address connectivity; parsing the configuration protocol to generate a parsing protocol, and verifying the configuration of the election policy based on the parsing protocol to generate a policy detection result; and using the connectivity test result and the policy detection result as the verification result corresponding to the configuration verification of maintaining an active service connection environment.

[0046] Among them, maintaining the active environment configuration verification of service connections refers to verifying the basic network status through the systematic use of network diagnostic tools (such as the ping command), ensuring the reachability of the virtual IP before IP virtualization, and verifying the correct configuration of the Master election strategy through automatic logical analysis of the VRRP protocol to ensure high availability.

[0047] Specifically, during verification, the controller can systematically use various network diagnostic tools, such as the ping command. By sending ICMP packets to the target node and receiving responses, the connectivity of the basic network can be evaluated, which helps to detect potential network problems in advance, such as link failures and congestion. In addition, before IP virtualization, it is necessary to ensure the reachability of the virtual IP. That is, verify that the data packets can be transmitted smoothly between the physical network and the virtual network. At the same time, automatic logical analysis of the VRRP protocol is also an important part of the verification process. The VRRP protocol is used to elect a Master router from a group of routers to be responsible for forwarding data packets. The configuration of the election strategy is verified through automatic logical analysis. Specifically, it can include checking whether the priority setting, preemption mode, timer configuration, etc. are correct. Only when the Master election strategy is configured correctly can it quickly switch to the backup router when the main router fails, thereby ensuring the high availability of the system and avoiding network interruptions or service unavailability.

[0048] In a specific embodiment, Figure 2 is a schematic diagram of a configuration verification process for maintaining an active service connection environment according to Embodiment 1 of the present invention. Figure 2 In the process of checking, the verification is started by calling a custom Python script. The necessary libraries (such as os, subprocess, etc.) can be imported through the custom Python script to execute external commands. According to the custom verification function and initialization configuration parameters, the subsequent verification tasks are started. Physical IP reachability detection refers to the connection test of the physical IP address by executing the ping operation through the system command under the guidance of the Python script. Ensuring that the IP is reachable lays the foundation for the continuity of subsequent network services. Virtual IP reachability detection refers to the connection test of the virtual IP using the ping command immediately after the physical IP to ensure that the network configuration after IP virtualization is correct and can effectively forward traffic to support the high availability requirements of the service. Automatically checking the Master election strategy in the VRRP protocol refers to automatically verifying whether the Master election strategy is configured correctly by parsing the VRRP configuration to ensure that when the master node fails, the backup node can quickly take over and keep the service running uninterruptedly.

[0049] Optionally, when the verification project is deployment configuration verification, the container orchestration engine to be tested is verified in turn according to each verification project to generate a verification result, including: taking each preset deployment configuration verification sub-project as a target verification sub-project in turn, wherein the deployment configuration verification sub-project includes version consistency verification, label uniqueness verification, name uniqueness verification, namespace consistency verification, replica quantity verification, template label integrity verification and image validity and pull strategy verification; traversing the deployment configuration of the container orchestration engine to be tested according to the target verification sub-project to determine each target field; obtaining the standard value corresponding to each target field, and determining the verification result corresponding to the deployment configuration verification according to the standard value and the target field.

[0050] Among them, deployment configuration verification refers to the use of logical algorithms to traverse the configuration file, compare the apiVersion version, check the uniqueness of the label and name, and the consistency of the resource name and image to ensure that the Deployment configuration logic is correct. At the same time, it will monitor the number of copies, resource restrictions, image download strategies, etc. to ensure that the resources and strategies are configured reasonably.

[0051] Specifically, the controller can use logical algorithms to traverse the configuration files. First, the consistency of the apiVersion versions will be compared. Different apiVersion versions may mean different functions and features. If the versions are inconsistent, the deployment may not proceed normally or unpredictable errors may occur. Checking the uniqueness of labels and names helps to accurately identify and manage each Deployment object in a complex system environment, avoiding confusion and errors caused by name conflicts. The verification process also closely monitors the number of replicas. Reasonable setting of the number of replicas can ensure the availability and performance of the application. Too many or too few replicas may affect the quality of the service. Namespace consistency verification refers to Namespace consistency confirmation.

[0052] In a specific embodiment, Figure 3This is a schematic diagram of a deployment configuration verification process provided according to the first embodiment of the present invention. The controller will first perform a unified service version check, that is, the script automatically scans all YAML configuration files on the business side, verifies the apiVersion field, and ensures that the apiVersion on the business side is consistent to avoid inconsistent service versions. When verifying the uniqueness of labels, you can traverse the metadata.labels in each Deployment configuration, use a hash set (HashSet) to record the label names that have appeared, and compare the new labels to ensure that the label attributes are globally unique, avoiding resource management confusion caused by label conflicts. When performing name uniqueness and consistency checks, you can check the Deployment names (metadata.name) one by one to ensure that there are no duplications, and check the Docker image names in spec.containers through the mapping relationship to ensure the logical consistency of the two names, which is convenient for tracking and management. When confirming the consistency of Namespace, you can check the metadata.namespace configurations of all business sides to confirm that they remain consistent to ensure that resources are deployed in the expected namespace, simplifying the management and permission control of cross-deployment resources. When checking the number of replicas, you can automatically review all spec.replicas settings to ensure that their value is greater than 3 to meet business continuity requirements and ensure that service availability is maintained even if some instances fail. When checking the integrity of template labels, you can deeply check the label configuration under spec.template.metadata to avoid duplication, while ensuring synchronization with the top-level metadata.labels to strengthen the consistency of label policies and the accuracy of resource selectors. When checking the validity and pull strategy of the image, you can use network requests to verify the Docker image URL in spec.containers to confirm that the image can be downloaded. At the same time, check the imagePullPolicy configuration and ensure that it is set to Always to automatically respond to image updates or service restart scenarios.

[0053] Optionally, when the verification item is service configuration verification, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: verifying the service configuration of the container to be tested according to preset service configuration verification sub-items to generate a verification result corresponding to the service configuration verification, wherein the service configuration verification sub-items include metadata consistency verification, port configuration consistency verification, internal port alignment verification, service type standardization verification and session affinity verification.

[0054] Among them, service configuration verification refers to verifying the consistency and correctness of the Service configuration, including metadata attribute matching with the Deployment, port alignment, internal port consistency, and standardization of service types and session persistence policies to ensure seamless connection between service discovery and load balancing.

[0055] Specifically, the controller will check the metadata attribute matching between the Service configuration and the Deployment. This includes confirming whether the metadata information such as the name, label, namespace, etc. of the same business module accurately corresponds between the two, ensuring that related services and deployment objects can be associated and identified in the system. Then it is also necessary to ensure that the port defined by the Service is exactly the same as the port actually exposed by the application in the Deployment, including port number, protocol type (such as TCP or UDP), etc. Any port mismatch may cause the service request to fail to be correctly routed to the application instance, thereby affecting the normal operation of the service. The internal port consistency check will confirm whether the port settings used to process traffic internally in the Service are in line with expectations and specifications, which can avoid data transmission errors or service function abnormalities due to confusion in internal ports.

[0056] In a specific embodiment, Figure 4 It is a schematic diagram of the service configuration verification process provided according to the first embodiment of the present invention; when performing metadata consistency verification, the script can be used to automatically compare the metadata attributes in the Service and the corresponding Deployment configuration to ensure that the metadata information such as the name and label in the same business module is completely consistent. When performing port configuration consistency verification, the script can be used to automatically check the consistency of the Service's spec.ports and the container port configuration in the Deployment, including the port number and protocol, to ensure that the service port is correctly exposed. When performing internal port alignment verification, the script can be used to automatically verify that the Service's spec.ports.targetPort is consistent with the container's internal port in the Deployment configuration to ensure that the traffic is correctly routed. When performing Service type standardization verification, the script can be used to automatically traverse and check the spec.type of all Services to confirm whether they are all configured as ClusterIP to meet the network security competition service discovery standards. When performing session affinity verification, the script can be used to automatically check the sessionAffinity attributes of all Services to ensure that they are set to None to avoid session stickiness problems in high concurrency scenarios.

[0057] Optionally, when the verification item is storage configuration verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: verifying the storage configuration of the container to be tested according to preset storage configuration verification sub-items to generate a verification result corresponding to the storage configuration verification, wherein the storage configuration verification sub-items include whether to perform mandatory verification of dynamic configuration management, configuration file format legality verification and character encoding standardization verification.

[0058] Among them, storage configuration verification refers to ConfigMap configuration verification, which is responsible for checking the format and encoding of dynamic configuration files to ensure the correctness of file syntax. At the same time, UTF-8 encoding is used to ensure the format standardization and readability of the configuration through automated management and verification.

[0059] In a specific embodiment, Figure 5 It is a schematic diagram of a storage configuration verification process provided according to the first embodiment of the present invention. When performing mandatory verification of dynamic configuration management, automatic verification can be performed through a script to ensure that all configuration files are managed through the ConfigMap mechanism of Kubernetes, to achieve separation of configuration and code, and to facilitate dynamic updates and version control. When performing a configuration file format legality check, all configuration files associated with ConfigMap can be automatically detected, and their grammatical correctness can be verified according to different file types to avoid configuration loading failures due to format errors. When performing character encoding standardization verification, cross-platform compatibility and internationalization support can be ensured by dynamically detecting whether all ConfigMap configuration files are encoded in UTF-8, and garbled characters can be avoided.

[0060] Optionally, when the verification item is a security verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: calling a preset verification script to determine the security policy startup status and network policy configuration status of the container orchestration engine to be tested; determining the sensitive information status of the configuration of the container orchestration engine to be tested according to the sensitive data list, wherein the sensitive data list includes database passwords and keys; and taking the security policy startup status, network policy configuration status and sensitive information status as the verification results corresponding to the security verification.

[0061] Among them, security verification refers to strengthening the configuration security line through automated policy review of the activation of PodSecurityPolicy, the deployment of Network Policy, and the correct use of Secrets, preventing unauthorized access and sensitive information leakage, and ensuring security compliance during container runtime.

[0062] In a specific embodiment, Figure 6It is a schematic diagram of a security verification process provided according to the first embodiment of the present invention. When verifying whether to enable PodSecurityPolicy, a script can be used to verify whether the system has enabled PodSecurityPolicy. Enabling PodSecurityPolicy allows for the implementation of detailed container runtime security specifications, limits container permissions, controls the use of Linux functions, limits access rights to the host machine, etc., fundamentally improving the security level of container operation. When verifying whether to configure Network Policy, a script can be used to automatically traverse the configuration of each application to check whether Network Policy is configured. This ensures that network traffic between Pods is strictly controlled to prevent unauthorized access, further strengthen network isolation, and improve communication security between services. When performing a security check on sensitive information, a script can be used to automatically check whether all sensitive information is properly managed through Kubernetes Secrets to prevent sensitive data such as database passwords, API keys, etc. from appearing in plain text in configuration files.

[0063] S120. Generate a verification report according to each verification result, and determine the configuration items to be adjusted according to the verification report.

[0064] Specifically, after completing the above verification items, the controller will generate a verification report based on the obtained verification results. The verification report includes the verification status of each verification item, which can show the performance of the container orchestration engine under test in different aspects.

[0065] Furthermore, the controller can determine the configuration items that need to be adjusted according to the verification report. The configuration items to be adjusted refer to the configurations that have failed a certain verification or have passed but still have room for optimization and improvement.

[0066] S130: Adjust the configuration of the container orchestration engine to be tested through the configuration items to be adjusted.

[0067] Specifically, the controller can divide the final verification results according to each verification item. For each category, first list all configuration items that have passed the verification, and at the same time list in detail the configuration items that have not passed the verification, that is, the configuration items to be adjusted, including specific error or alarm descriptions, the names and line numbers of the services or configuration files involved, to ensure the accuracy of problem location. For example, point out the specific value of the resource request in a specific Deployment that exceeds the node capacity, or the details of the port mapping mismatch in the Service configuration.

[0068] Furthermore, for the configuration items to be adjusted, we can provide in-depth technical analysis based on the database to explain why the configuration items are not compliant, such as the potential impact of excessive resource restrictions, communication barriers that may be caused by network configuration conflicts, etc., and put forward specific correction suggestions, including but not limited to adjusting resource quotas, modifying configuration parameters, correcting naming rules, updating security policies, etc. For each suggestion, a concise operation guide is attached, such as specific commands for adjusting CPU or memory limits, steps for resolving naming conflicts, etc., to speed up problem solving.

[0069] It should be noted that in the context of the current cybersecurity competition using Kubernetes for service cluster management, although it provides high flexibility and scalability, there are significant challenges and defects in configuration automation verification. These defects directly hinder the efficient and stable operation of the cybersecurity competition system, which is specifically manifested in the following aspects: 1. High configuration complexity leads to increased error probability: Kubernetes configuration files use the YAML format, which is more complex than Docker-compose and involves many configuration items, including service definition, resource restrictions, network policies, security configuration, etc. The increase in configuration items directly leads to a significant increase in the possibility of errors in the manual writing and review process, such as configuration omissions, misconfiguration, etc., which seriously affect system deployment and operation. 2. Inefficient and inaccurate manual review: Traditional configuration checks rely on manual review, which is particularly inefficient in the face of Kubernetes' complex configuration. Manual review is not only time-consuming, but also limited by personal knowledge and experience. It is difficult to ensure the accuracy of all configurations, and it is easy to ignore minor errors, causing subsequent deployment problems. 3. Delayed discovery of configuration problems: The passive method of relying on log analysis after the service is started to discover configuration errors leads to delayed problem discovery, which can only be detected when the service actually fails or is abnormal. This post-investigation not only increases the cost and time of problem repair, but may also cause business interruptions, seriously affecting the continuity of network security competitions and user experience. 4. Insufficient resource management and security configuration: If the resource allocation (CPU, memory) in the Kubernetes configuration is unreasonable, it may lead to excessive or insufficient resource consumption, affecting system performance. In addition, security configurations such as inappropriate settings of PodSecurityPolicy and NetworkPolicy, as well as improper handling of sensitive information, will bring security risks and increase vulnerability to attacks. 5. Poor compliance with standardization and best practices: In the absence of automated verification, it is difficult to ensure that all configurations follow best practices, such as label naming consistency, version uniformity, mirroring strategies, etc. This not only affects management efficiency, but may also bury potential operational risks.

[0070] In summary, the technical solution of the embodiment of the present invention constructs a comprehensive automated verification method to comprehensively and systematically check various configurations before the Kubernetes cluster is deployed to ensure the correctness, efficiency and security of the configuration, thereby achieving the following core purposes: 1. Improve configuration accuracy: Use automated tools to achieve in-depth analysis and verification of Kubernetes configurations, including but not limited to keepAlive environment, Deployment, Service, ConfigMap, security configuration, etc., to ensure that all configuration items are accurate and reduce the deployment error rate. 2. Improve efficiency and timeliness: Automatically complete configuration verification before the service is started, and immediately feedback the problem. Compared with traditional manual review and post-operation log analysis, it significantly shortens the problem discovery cycle and reduces resource waste and business interruption risks. 3. Optimize resource and security configuration: Automatically evaluate the rationality of resource allocation to avoid overbooking or underbooking of resources, and at the same time strengthen security policy checks to ensure the correct configuration of PodSecurityPolicy and Network Policy, as well as the proper management of sensitive information through Secrets, to enhance the overall security defense capabilities of the system. 4. Promote standardized practices: The automated verification process is based on best practice standards to ensure consistency in configuration naming, version control, image strategy, etc., improve the standardization level of system management, and lay a solid foundation for the stable operation and maintenance of network security competitions.

[0071] The technical solution of the embodiment of the present invention ensures the correctness, efficiency and security of the configuration by comprehensively and systematically verifying various configurations before the container orchestration engine cluster is deployed. The verification items include maintaining the active environment configuration verification of service connections, deployment configuration verification, service configuration verification, storage configuration verification and security verification, which improves the accuracy of the configuration and significantly improves the verification efficiency, ensuring the early discovery and immediate correction of configuration problems. By adjusting the configuration of the configuration items to be adjusted, the operation and maintenance efficiency and the overall performance of the system are further improved.

[0072] Embodiment 2

[0073] Figure 7 This is a flowchart of a container orchestration engine configuration verification method provided in the second embodiment of the present invention. This embodiment adds a verification report based on each verification result and determines the configuration items to be adjusted based on the verification report. The specific content of step S210 is roughly the same as step S110 in the first embodiment, so it will not be repeated in this embodiment. Figure 7 As shown, the method includes:

[0074] S210. Verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining service connection active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification.

[0075] Optionally, when the verification item is to verify the configuration of maintaining an active service connection environment, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: calling a preset command to perform a connectivity test on the container orchestration engine to be tested to generate a connectivity test result, wherein the connectivity test result includes physical address connectivity and virtual address connectivity; parsing the configuration protocol to generate a parsing protocol, and verifying the configuration of the election policy based on the parsing protocol to generate a policy detection result; and using the connectivity test result and the policy detection result as the verification result corresponding to the configuration verification of maintaining an active service connection environment.

[0076] Optionally, when the verification project is deployment configuration verification, the container orchestration engine to be tested is verified in turn according to each verification project to generate a verification result, including: taking each preset deployment configuration verification sub-project as a target verification sub-project in turn, wherein the deployment configuration verification sub-project includes version consistency verification, label uniqueness verification, name uniqueness verification, namespace consistency verification, replica quantity verification, template label integrity verification and image validity and pull strategy verification; traversing the deployment configuration of the container orchestration engine to be tested according to the target verification sub-project to determine each target field; obtaining the standard value corresponding to each target field, and determining the verification result corresponding to the deployment configuration verification according to the standard value and the target field.

[0077] Optionally, when the verification item is service configuration verification, the container orchestration engine to be tested is verified in sequence according to each verification item to generate a verification result, including: verifying the service configuration of the container to be tested according to preset service configuration verification sub-items to generate a verification result corresponding to the service configuration verification, wherein the service configuration verification sub-items include metadata consistency verification, port configuration consistency verification, internal port alignment verification, service type standardization verification and session affinity verification.

[0078] Optionally, when the verification item is storage configuration verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: verifying the storage configuration of the container to be tested according to preset storage configuration verification sub-items to generate a verification result corresponding to the storage configuration verification, wherein the storage configuration verification sub-items include whether to perform mandatory verification of dynamic configuration management, configuration file format legality verification and character encoding standardization verification.

[0079] Optionally, when the verification item is a security verification, the container orchestration engine to be tested is verified in turn according to each verification item to generate a verification result, including: calling a preset verification script to determine the security policy startup status and network policy configuration status of the container orchestration engine to be tested; determining the sensitive information status of the configuration of the container orchestration engine to be tested according to the sensitive data list, wherein the sensitive data list includes database passwords and keys; and taking the security policy startup status, network policy configuration status and sensitive information status as the verification results corresponding to the security verification.

[0080] S220, determining the target verification item corresponding to each verification result.

[0081] S230: Obtain a verification report template, and determine a target position corresponding to a target verification item in the verification report template.

[0082] S240. Combine the corresponding verification results with the verification report template according to the target position to generate a verification report.

[0083] S250, determine whether there are any abnormal items in the verification report, if so, execute S260, otherwise, execute S270.

[0084] S260. Treat the abnormal item as a configuration item to be adjusted.

[0085] S270: Determine that there is no configuration item to be adjusted.

[0086] Specifically, the controller will clarify the target verification items corresponding to each verification result. Then determine the specific position of the target verification item in the template, that is, the target position. By determining the target position, the verification result can be accurately placed in the correct position. Then the controller can combine the corresponding verification results with the verification report template according to the determined target position. In the process of combining, the accuracy and completeness of the data must be guaranteed so that the generated verification report can clearly and accurately reflect the verification situation. The controller can make a comprehensive judgment and analysis of the generated verification report to see if there are any abnormal items. Abnormal items usually refer to those that do not meet expectations, have problems, or require further attention and processing. If abnormal items are found, these abnormal items will be used as configuration items to be adjusted so that targeted adjustments and optimizations can be made later. If it is judged that there are no abnormal items in the verification report, then it is determined that the configuration items to be adjusted are none, which means that the current verification situation is good and no additional adjustment and configuration work is required.

[0087] Furthermore, whether there are abnormal items in the verification report can be determined by setting clear standards and thresholds: before conducting the verification, reasonable standards and thresholds should be set for each verification item based on business needs, industry specifications or past experience, which can be numerical ranges, specific conditions or rules. Then compare the data in the verification report with the set standards and thresholds. For example, if it is numerical data, check whether it exceeds the upper and lower limits allowed; if it is conditional data, determine whether it meets the preset conditions. It can also be done by observing the trends and patterns of the data. If an indicator shows abnormal growth, decline or fluctuation over a period of time, it means that an abnormality may occur. In addition, the data in the current verification report can be compared with the verification report data in the same period or similar scenarios in history. If there is a significant difference, it can be determined as an abnormal item.

[0088] The technical solution of the embodiment of the present invention ensures the correctness, efficiency and security of the configuration by comprehensively and systematically verifying various configurations before the container orchestration engine cluster is deployed. The verification items include maintaining the active environment configuration verification of service connections, deployment configuration verification, service configuration verification, storage configuration verification and security verification, which improves the accuracy of the configuration and significantly improves the verification efficiency, ensuring the early discovery and immediate correction of configuration problems. By adjusting the configuration of the configuration items to be adjusted, the operation and maintenance efficiency and the overall performance of the system are further improved.

[0089] Embodiment 3

[0090] Fig. 9 This is a schematic diagram of a container orchestration engine configuration verification device provided by Embodiment 3 of the present invention. Fig. 9 As shown, the device includes: a verification result generating module 310, which is used to verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining service connection active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification;

[0091] The configuration item to be adjusted determining module 320 is used to generate a verification report according to each of the verification results, and determine the configuration item to be adjusted according to the verification report;

[0092] The configuration adjustment module 330 is used to adjust the configuration of the container orchestration engine to be tested through the configuration item to be adjusted.

[0093] Optionally, the verification result generation module 310 specifically includes: a service connection maintenance active environment configuration verification unit, which is used to: call a preset command to perform a connectivity test on the container orchestration engine to be tested to generate a connectivity test result, wherein the connectivity test result includes physical address connectivity and virtual address connectivity; parse the configuration protocol to generate a parsing protocol, and verify the configuration of the election strategy based on the parsing protocol to generate a policy detection result; and use the connectivity test result and the policy detection result as the verification result corresponding to the service connection maintenance active environment configuration verification.

[0094] Optionally, the verification result generation module 310 specifically includes: a deployment configuration verification unit, which is used to: sequentially use each preset deployment configuration verification sub-item as a target verification sub-item, wherein the deployment configuration verification sub-item includes version consistency verification, label uniqueness verification, name uniqueness verification, namespace consistency verification, replica quantity verification, template label integrity verification and image validity and pull strategy verification; traverse the deployment configuration of the container orchestration engine to be tested according to the target verification sub-item to determine each target field; obtain the standard value corresponding to each target field, and determine the verification result corresponding to the deployment configuration verification according to the standard value and the target field.

[0095] Optionally, the verification result generation module 310 specifically includes: a service configuration verification unit, which is used to: verify the service configuration of the container to be tested according to preset service configuration verification sub-items to generate a verification result corresponding to the service configuration verification, wherein the service configuration verification sub-items include metadata consistency verification, port configuration consistency verification, internal port alignment verification, service type standardization verification and session affinity verification.

[0096] Optionally, the verification result generation module 310 specifically includes: a storage configuration verification unit, which is used to: verify the storage configuration of the container to be tested according to preset storage configuration verification sub-items to generate a verification result corresponding to the storage configuration verification, wherein the storage configuration verification sub-items include whether to perform dynamic configuration management mandatory verification, configuration file format legality verification and character encoding standardization verification.

[0097] Optionally, the verification result generation module 310 specifically includes: a security verification unit, which is used to: call a preset verification script to determine the security policy startup status and network policy configuration status of the container orchestration engine to be tested; determine the sensitive information status of the configuration of the container orchestration engine to be tested according to the sensitive data list, wherein the sensitive data list includes database passwords and keys; and use the security policy startup status, network policy configuration status and sensitive information status as verification results corresponding to the security verification.

[0098] Optionally, the module 320 for determining the configuration items to be adjusted is specifically used to: determine the target verification items corresponding to each verification result; obtain the verification report template, and determine the target position corresponding to the target verification item in the verification report template; combine the corresponding verification results and the verification report template according to the target position to generate a verification report; determine whether there are abnormal items in the verification report, and if so, treat the abnormal items as configuration items to be adjusted; otherwise, determine that there are no configuration items to be adjusted.

[0099] The technical solution of the embodiment of the present invention ensures the correctness, efficiency and security of the configuration by comprehensively and systematically verifying various configurations before the container orchestration engine cluster is deployed. The verification items include maintaining the active environment configuration verification of service connections, deployment configuration verification, service configuration verification, storage configuration verification and security verification, which improves the accuracy of the configuration and significantly improves the verification efficiency, ensuring the early discovery and immediate correction of configuration problems. By adjusting the configuration of the configuration items to be adjusted, the operation and maintenance efficiency and the overall performance of the system are further improved.

[0100] A container orchestration engine configuration verification device provided by an embodiment of the present invention can execute a container orchestration engine configuration verification method provided by any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0101] Embodiment 4

[0102] Fig.10 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0103] like Fig.10As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0104] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0105] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a container orchestration engine configuration verification method.

[0106] In some embodiments, a container orchestration engine configuration verification method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the container orchestration engine configuration verification method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute a container orchestration engine configuration verification method in any other appropriate manner (e.g., by means of firmware).

[0107] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0108] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0109] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0110] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0111] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0112] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0113] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0114] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A container orchestration engine configuration verification method, applied to network security competition scenarios, characterized in that: include: Verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining active service connection environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification; Generate a verification report according to each of the verification results, and determine the configuration items to be adjusted according to the verification report; The configuration of the container orchestration engine to be tested is adjusted through the configuration item to be adjusted.

2. The method according to claim 1, characterized in that When the verification item is to maintain the active environment configuration verification of the service connection, the verification of the container orchestration engine to be tested is performed in sequence according to each verification item to generate a verification result, including: Calling a preset command to perform a connectivity test on the container orchestration engine to be tested to generate a connectivity test result, wherein the connectivity test result includes physical address connectivity and virtual address connectivity; Parsing the configuration protocol to generate a parsing protocol, and verifying the configuration of the election strategy based on the parsing protocol to generate a strategy detection result; The connectivity test result and the policy detection result are used as verification results corresponding to the configuration verification of maintaining the active environment for the service connection.

3. The method according to claim 1, characterized in that When the verification item is deployment configuration verification, the verification of the container orchestration engine to be tested is performed in sequence according to each verification item to generate a verification result, including: Each preset deployment configuration verification sub-item is used as the target verification sub-item in turn, wherein the deployment configuration verification sub-item includes version consistency verification, label uniqueness verification, name uniqueness verification, namespace consistency verification, replica quantity verification, template label integrity verification, and image validity and pull strategy verification; According to the target verification sub-item, the deployment configuration of the container orchestration engine to be tested is traversed to determine each target field; The standard value corresponding to each of the target fields is obtained, and the verification result corresponding to the deployment configuration verification is determined according to the standard value and the target field.

4. The method according to claim 1, characterized in that When the verification item is service configuration verification, the verification of the container orchestration engine to be tested is performed in sequence according to each verification item to generate a verification result, including: The service configuration of the container to be tested is verified according to the preset service configuration verification sub-item to generate a verification result corresponding to the service configuration verification, wherein the service configuration verification sub-item includes metadata consistency verification, port configuration consistency verification, internal port alignment verification, service type standardization verification and session affinity verification.

5. The method according to claim 1, characterized in that When the verification item is storage configuration verification, the verification of the container orchestration engine to be tested is performed in sequence according to each verification item to generate a verification result, including: The storage configuration of the container to be tested is verified according to the preset storage configuration verification sub-item to generate a verification result corresponding to the storage configuration verification, wherein the storage configuration verification sub-item includes whether to perform dynamic configuration management mandatory verification, configuration file format legality verification and character encoding standardization verification.

6. The method according to claim 1, characterized in that When the verification item is a security verification, the verification of the container orchestration engine to be tested is performed in sequence according to each verification item to generate a verification result, including: Calling a preset verification script to determine the security policy startup status and network policy configuration status of the container orchestration engine to be tested; Determine the sensitive information of the configuration of the container orchestration engine to be tested according to the sensitive data list, wherein the sensitive data list includes database passwords and keys; The security policy startup status, network policy configuration status and sensitive information status are used as verification results corresponding to the security verification.

7. The method according to claim 1, characterized in that Generating a verification report according to each of the verification results, and determining the configuration items to be adjusted according to the verification report, includes: Determine the target verification items corresponding to each verification result; Obtain a verification report template, and determine a target position corresponding to the target verification item in the verification report template; Combining the corresponding verification results with the verification report template according to the target location to generate the verification report; Determine whether there are abnormal items in the verification report, and if so, use the abnormal items as the configuration items to be adjusted; Otherwise, it is determined that the configuration item to be adjusted is none.

8. A container orchestration engine configuration verification device, applied to network security competition scenarios, characterized in that: include: A verification result generation module is used to verify the container orchestration engine to be tested in turn according to each verification item to generate a verification result, wherein the verification items include maintaining service connection active environment configuration verification, deployment configuration verification, service configuration verification, storage configuration verification and security verification; A module for determining configuration items to be adjusted, used to generate a verification report according to each of the verification results, and determine the configuration items to be adjusted according to the verification report; A configuration adjustment module is used to adjust the configuration of the container orchestration engine to be tested through the configuration item to be adjusted.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 7.

10. A computer storage medium, characterized in that: The computer storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method according to any one of claims 1 to 7 when executed.

Citation Information

Patent Citations

  • Method and device for deploying Kubernetes cluster

    CN110502244A

  • Intelligent orchestration and flexible scale using containers for application deployment and elastic service

    US20180205616A1