A cloud-native container platform integration method and system

Abstract

The application provides a cloud-native container platform integration method and system, and belongs to the technical field of cloud computing, and comprises the following steps: determining a running environment of a cloud-native container platform event flow; in the running environment, determining a workflow template based on a continuous integration and continuous deployment process; deploying an event trigger in a code repository based on the workflow template; and triggering the cloud-native container platform event flow by using the event trigger. The application is based on a Kubernetes platform, realizes a continuous integration process of original code, arranges a continuous integration and continuous deployment process through an event flow, predefines an event flow template, triggers an event flow to run by injecting parameters through a command line, and relies on flexible arrangement of the event flow to realize complex mathematical calculation and a flexible and open event flow processing mechanism.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and in particular to a cloud-native container platform integration method and system. Background Technology

[0002] Kubernetes, a container orchestration engine, is used to manage containerized applications across multiple hosts in a cloud platform. It's an open-source platform that enables automated deployment, scaling, and maintenance of container clusters. Kubernetes allows for rapid application deployment; rapid application scaling; seamless integration with new application features while saving resources; and optimized hardware resource usage. Kubernetes features include: multiple pods working together; storage system mounting; application health checks; application instance replication; pod autoscaling / scaling; registration and discovery; load balancing; rolling updates; resource monitoring; log access; application debugging; and authentication and authorization.

[0003] CI / CD is a concept in continuous software integration. The development and delivery of a systematic software inevitably involves the continuous integration and merging of new functions and the continuous verification of applications.

[0004] Workflow is an event-driven workflow, which is a logical arrangement of existing fixed workflows. Argo, as a workflow controller, has the advantage of being able to design high-concurrency, multi-step workflows. Furthermore, the workflow engine is a DAG, which can build complex workflow logic. The advantage of Argo-workflow is that it can implement some non-linear task logic. Complex data operations and data relationships in CI processes can be implemented through it.

[0005] Event is a detailed event forwarding mechanism that can capture different event sources, forward them to our pre-defined event interceptors, and finally trigger the CI / CD workflow.

[0006] However, existing technologies lack a systematic approach for integrating with cloud-native container platforms. Summary of the Invention

[0007] This invention provides a cloud-native container platform integration method and system to address the deficiency in the prior art of lacking a systematic method for triggering event streams on cloud-native container platforms.

[0008] In a first aspect, the present invention provides a cloud-native container platform integration method, comprising:

[0009] Determine the runtime environment for the event stream of the cloud-native container platform;

[0010] In the aforementioned operating environment, workflow templates are determined based on continuous integration and continuous deployment processes;

[0011] Based on the workflow template, deploy event triggers in the code repository;

[0012] The event trigger is used to trigger the cloud-native container platform event stream.

[0013] According to a cloud-native container platform integration method provided by the present invention, determining the runtime environment of the cloud-native container platform event stream includes:

[0014] Create a Kubernetes cluster for container orchestration engines, which includes control nodes and worker nodes;

[0015] The container-local workflow engine argo-workflow is deployed using the package management tool Helm and an offline image deployment mode.

[0016] The argo command line is deployed using binary mode, and the argo-event engine is deployed using Helm.

[0017] The argo-workflow and the argo-event engine use the same command space.

[0018] According to a cloud-native container platform integration method provided by the present invention, the step of determining a workflow template based on continuous integration and continuous deployment processes in the runtime environment includes:

[0019] Create an execution step template based on the continuous integration and continuous deployment process, and obtain the storage status of the continuous integration and continuous deployment process;

[0020] The execution step template is output in container pod mode to form the workflow template.

[0021] According to a cloud-native container platform integration method provided by the present invention, the step of deploying event triggers in the code repository based on the workflow template includes:

[0022] Deploy a reverse push interface webhook in the code repository, and determine the EventBus component and Sensor component based on the address of the webhook;

[0023] The event source (eventsource) is obtained from the EventBus component, and the event trigger is created based on the Sensor component and the event source.

[0024] According to the cloud-native container platform event flow triggering method provided by the present invention, after deploying the event trigger in the code repository based on the workflow template, the method further includes:

[0025] Create an event;

[0026] Based on the event, the event trigger automatically triggers the cloud-native container platform event stream.

[0027] According to a cloud-native container platform integration method provided by the present invention, the step of triggering the cloud-native container platform event stream using the event trigger includes:

[0028] Execute push and merge operations in the code repository, and obtain pod runtime logs for the continuous integration and continuous deployment process through the event triggers;

[0029] The runtime status of the cloud-native container platform event stream is obtained based on the pod runtime logs.

[0030] Secondly, the present invention also provides a cloud-native container platform integration system, comprising:

[0031] The first determination module is used to determine the runtime environment of the cloud-native container platform event stream;

[0032] The second determining module is used to determine a workflow template based on the continuous integration and continuous deployment processes in the operating environment.

[0033] The deployment module is used to deploy event triggers in the code repository based on the workflow template;

[0034] The triggering module is used to trigger the event stream of the cloud-native container platform using the event trigger.

[0035] Thirdly, the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the cloud-native container platform integration method described above.

[0036] Fourthly, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the cloud-native container platform integration method as described above.

[0037] Fifthly, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the cloud-native container platform integration method described above.

[0038] The cloud-native container platform integration method and system provided by this invention realizes the continuous integration process of native code based on the Kubernetes platform. It achieves continuous integration and continuous deployment through event flow orchestration, predefines event flow templates, triggers event flow execution by injecting parameters through command line, and realizes complex mathematical calculations and a flexible and open event flow processing mechanism by relying on the flexible orchestration of event flow. Attached Figure Description

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

[0040] Figure 1 This is one of the flowcharts illustrating the cloud-native container platform integration method provided by the present invention;

[0041] Figure 2 This is a logical diagram illustrating the workflow implementation provided by the present invention;

[0042] Figure 3 This is a schematic diagram of the event-triggered workflow provided by the present invention;

[0043] Figure 4 This is the second flowchart illustrating the cloud-native container platform integration method provided by the present invention;

[0044] Figure 5 This is a schematic diagram of the structure of the cloud-native container platform integration system provided by the present invention;

[0045] Figure 6 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0047] The following is combined Figures 1-6 The present invention describes the cloud-native container platform integration method.

[0048] To address the problems existing in the prior art, the present invention provides an integration method based on a cloud-native container platform for continuous integration, which does not require containerization deployment around Jenkins, and can achieve the basic functions of the continuous integration process.

[0049] Figure 1 This is one of the flowcharts illustrating the cloud-native container platform integration method provided by the present invention, such as... Figure 1 As shown, it includes:

[0050] Step 100: Determine the runtime environment for the cloud-native container platform event stream;

[0051] Step 200: In the operating environment, determine the workflow template based on the continuous integration and continuous deployment processes;

[0052] Step 300: Based on the workflow template, deploy event triggers in the code repository;

[0053] Step 400: Utilize the event trigger to trigger the cloud-native container platform event stream.

[0054] Specifically, this invention creates a Kubernetes cluster, with node types including control nodes and compute nodes. The cluster deployment is based on cloud-native Argo workflow and Argo events components. After deployment, a CI / CD workflow is created according to requirements. The event flow can be modified according to actual needs, allowing for relatively flexible logic implementation. After workflow customization and creation, event-related resources are created based on the event source. This invention uses GitLab as the event source, triggering the CI / CD workflow based on triggering conditions. The overall system also includes monitoring GitLab code to automatically trigger events, defining the Argo-event-related event bus and sensors for GitLab triggering operations, and customizing CI / CD workflow templates.

[0055] The entire solution avoids the drawbacks of containerized Jenkins deployment. All basic components are cloud-native, reducing the difficulties brought about by containerized CI process builds and tool deployment. It has independent page and command-line interaction methods, and can track the build process in real time.

[0056] It should be noted that Argo is an open-source container-native workflow engine used to perform tasks on Kubernetes, and it has the following features:

[0057] Define a workflow in which each step is a container;

[0058] Model multi-step workflows as a series of tasks, or use a graph (DAG) to capture the dependencies between tasks;

[0059] Using the argo workflow on Kubernetes, computationally intensive jobs can be easily run in a very short time for machine learning or data processing.

[0060] Run CI / CD pipelines locally on Kubernetes without configuring complex software development products.

[0061] This invention enables continuous integration of native code based on the Kubernetes platform. Through event stream orchestration for continuous integration and continuous deployment, it predefines event stream templates, triggers event stream execution by injecting parameters via command line, and realizes complex mathematical calculations and a flexible and open event stream processing mechanism by relying on the flexible orchestration of event streams.

[0062] Based on the above embodiments, determining the runtime environment of the cloud-native container platform event stream includes:

[0063] Create a Kubernetes cluster for container orchestration engines, which includes control nodes and worker nodes;

[0064] The container-local workflow engine argo-workflow is deployed using the package management tool Helm and an offline image deployment mode.

[0065] The argo command line is deployed using binary mode, and the argo-event engine is deployed using Helm.

[0066] The argo-workflow and the argo-event engine use the same command space.

[0067] Specifically, before running, the relevant platform environment needs to be created, including creating a Kubernetes cluster containing master and worker nodes, i.e., control nodes and worker nodes; and deploying argo-workflow and argo-events.

[0068] In deploying argo-workflow, this invention employs a deployment method using Helm packages and offline images, resulting in more stable deployment. Helm, developed by Deis, is a package management tool for Kubernetes applications, primarily used to manage charts, similar to APT in Ubuntu or YUM in CentOS. Helm charts are a series of YAML files used to encapsulate native Kubernetes applications, allowing customization of application metadata during deployment to facilitate application distribution. For application publishers, Helm can be used to package applications, manage application dependencies, manage application versions, and publish applications to software repositories. For users, using Helm eliminates the need to write complex application deployment files, enabling a simple way to find, install, upgrade, rollback, and uninstall applications on Kubernetes.

[0069] When deploying the argo command line, because the command line is a binary deployment, it needs to be matched with the image. Therefore, a unified configuration has not been implemented in this invention.

[0070] When deploying the argo-event engine, it is designed to be installed and deployed using Helm packages, just like workflow, and both components use the same command space.

[0071] This invention is based on Kubernetes and deploys multiple components through the container-native workflow engine argo to ensure the triggering process of event flow on the cloud-native container platform.

[0072] Based on the above embodiments, the step of determining the workflow template in the operating environment based on continuous integration and continuous deployment processes includes:

[0073] Create an execution step template based on the continuous integration and continuous deployment process, and obtain the storage status of the continuous integration and continuous deployment process;

[0074] The execution step template is output in container pod mode to form the workflow template.

[0075] Furthermore, this invention also creates CI / CD tasks based on Continuous Integration / Continuous Deployment (CI / CD) templates. Workflows are then created from these tasks. A WorkflowTemplate is designed based on the CI / CD process, packaged into a pod, and its resource type is WorkflowTemplate. This includes the CI / CD process execution steps and storage status, and can interact with the cluster's storage resources. The CI / CD process offers advantages for workflow implementation, allowing for complex logic control and supporting timeouts, loops, parallelism, and replay mechanisms. Each step template is created based on the CI / CD process, and the WorkflowTemplate is implemented based on these step templates. The core engine DAG in the workflow orchestration provides orchestration flexibility.

[0076] like Figure 2 As shown, Workflow includes several key concepts: WorkflowTemplate, Workflow, and template. The template defines a set of runtime logic, including scripts, containers, process control DAGs, and Kubernetes resources. It is implemented using multiple Kubernetes pod groups, which not only define the workflow but also store its runtime status. WorkflowTemplate is a workflow template library containing templates for specific business logic and implementation. This invention implements two WorkflowTemplates: one for CI (Computer Interaction) and one for CD (Computer Deployment) processes. After listening to an event source, the defined CI WorkflowTemplate is triggered via the event. After the CI process completes, the compiled version is uploaded to the specified repository, triggering the CD process.

[0077] This invention fully leverages the advantages of flexible workflow orchestration by using a predefined WorkflowTemplate and injecting parameters via the command line to trigger workflow execution.

[0078] Based on the above embodiments, the step of deploying event triggers in the code repository based on the workflow template includes:

[0079] Deploy a reverse push interface webhook in the code repository, and determine the EventBus component and Sensor component based on the address of the webhook;

[0080] The event source (eventsource) is obtained from the EventBus component, and the event trigger is created based on the Sensor component and the event source.

[0081] The step of deploying event triggers in the code repository based on the workflow template further includes:

[0082] Create an event;

[0083] Based on the event, the event trigger automatically triggers the cloud-native container platform event stream.

[0084] Specifically, such as Figure 3 As shown, the event-triggered workflow proposed in this invention includes:

[0085] A predefined eventsource is a webhook configured on the GitLab server, which is triggered every time code is pushed or merged from the Git repository. EventBus can be viewed as a message queue for events. EventSource sends events to EventBus, Sensors subscribe to the EventBus message queue, and EventBus forwards the events to Sensor components that have subscribed to them. Sensor components register and associate with one or more triggers, which can trigger AWS Lambda events and Argo Workflow events.

[0086] This involves the details of event triggering implementation, sensor customization, event interceptor implementation, cluster resources, and cluster component customization. It also allows for the customization and integration of trigger policies, making the entire event logic compatible with the cluster and scalable.

[0087] Here, a webhook is a URL that receives HTTP POST (or GET, PUT, DELETE) requests. An API provider that implements a webhook sends a message to this configured URL when an event occurs. Unlike request-response models, webhooks allow for real-time updates. This is another reversal of the client-server model. In the traditional approach, the client requests data from the server, and the server provides the data to the client. In the webhook paradigm, the server updates the necessary resources and automatically sends them as updates to the client (the server is pushing data). The client is not the requester but a passive receiver. This reversal of control can facilitate many communication requests that would otherwise require more complex requests and constant polling on a remote server. By simply receiving resources instead of sending requests directly, remote codebases can be updated, resources can be easily allocated, and even integrated into existing systems to update endpoints and related data as needed by the API.

[0088] This invention enables automatic triggering of workflows by event triggers. In the complete cloud-native implementation scheme, it realizes the entire implementation scheme of native workflow implementation, external trigger implementation, and external triggering of native workflow.

[0089] Based on the above embodiments, the step of triggering the cloud-native container platform event stream using the event trigger includes:

[0090] Execute push and merge operations in the code repository, and obtain pod runtime logs for the continuous integration and continuous deployment process through the event triggers;

[0091] The runtime status of the cloud-native container platform event stream is obtained based on the pod runtime logs.

[0092] Specifically, such as Figure 4 As shown, this invention also deploys a Git event triggering process, configuring a Git pushmerge webhook in the Git repository. Based on the address defined in the webhook, an EventBus and sensor are defined, enabling the Git event source to generate the corresponding eventbus, and triggering the event based on the defined sensor. Since the entrypoints included in the workflow require injected parameters to run, parameter templates are predefined during the event design process, and the parameters are finally loaded and passed to the workflow during event triggering.

[0093] When performing code push or merge operations in the code repository, you can view the pod running logs corresponding to the CI / CD process through the workflow page or command line. The page shows different display for different event running states, and finally, the workflow page executes a new workflow.

[0094] GitLab, mentioned here, is an open-source project for repository management systems. It uses Git as the code management tool and builds a web service on top of it. Installation instructions can be found on the GitLab Wiki page on GitHub. GitLab is a widely used open-source code management platform based on Git, built on Ruby on Rails. It primarily manages code and documentation generated during software development. GitLab manages code and documentation along two dimensions: groups and projects. A group can manage multiple projects, which can be understood as a group containing multiple software development tasks. A project may contain multiple branches, meaning each project has multiple independent branches that can be merged.

[0095] In addition, this invention also monitors workflow execution through a dashboard, creates resources through command-line interaction, and enables extended functions such as capturing pod alarms and generating cluster alarms. It provides flexible orchestration based on pages and operable command lines, and enables page submission of resources and template customization.

[0096] This invention, based on the Kubernetes platform, enables native continuous integration. It orchestrates CI / CD processes through workflows, predefined WorkflowTemplates, and allows command-line parameter injection to trigger workflow execution. Furthermore, it utilizes event sources, including push and merge events defined by GitLab webhooks, and an eventbus sensor design that implements message queues and message interception filtering rules. Finally, injected parameters complete the workflow execution. The advantages of this invention lie in its flexible workflow orchestration, which not only meets general CI / CD process requirements but also, due to its DAG engine, enables complex mathematical calculations, making it more powerful in this aspect. Event customization is also more flexible; resources and components within the Kubernetes cluster, as well as common CI components such as GitLab, AWS-SNS, and AWS-SQS, can all serve as event sources. Sensors and trigger policies can also be customized, resulting in a flexible and open event mechanism. It also provides greater convenience through rich visual interfaces and interactive command lines.

[0097] The cloud-native container platform integration system provided by the present invention is described below. The cloud-native container platform integration system described below and the cloud-native container platform integration method described above can be referred to in correspondence.

[0098] Figure 5 This is a schematic diagram of the structure of the cloud-native container platform integration system provided by the present invention, as shown below. Figure 5 As shown, it includes: a first determining module 51, a second determining module 52, a deployment module 53, and a triggering module 54, wherein:

[0099] The first determining module 51 is used to determine the operating environment of the cloud-native container platform event flow; the second determining module 52 is used to determine a workflow template based on continuous integration and continuous deployment processes in the operating environment; the deployment module 53 is used to deploy event triggers in the code repository based on the workflow template; and the triggering module 54 is used to trigger the cloud-native container platform event flow using the event triggers.

[0100] This invention enables continuous integration of native code based on the Kubernetes platform. Through event stream orchestration for continuous integration and continuous deployment, it predefines event stream templates, triggers event stream execution by injecting parameters via command line, and realizes complex mathematical calculations and a flexible and open event stream processing mechanism by relying on the flexible orchestration of event streams.

[0101] Figure 6An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 6 As shown, the electronic device may include a processor 610, a communications interface 620, a memory 630, and a communication bus 640, wherein the processor 610, communications interface 620, and memory 630 communicate with each other via the communication bus 640. The processor 610 can invoke logical instructions in the memory 630 to execute a cloud-native container platform integration method. This method includes: determining the runtime environment of the cloud-native container platform event flow; determining a workflow template based on continuous integration and continuous deployment processes within the runtime environment; deploying event triggers in the code repository based on the workflow template; and triggering the cloud-native container platform event flow using the event triggers.

[0102] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0103] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer is able to execute the cloud-native container platform integration method provided by the above methods. The method includes: determining the operating environment of the cloud-native container platform event flow; determining a workflow template based on continuous integration and continuous deployment processes in the operating environment; deploying event triggers in a code repository based on the workflow template; and triggering the cloud-native container platform event flow using the event triggers.

[0104] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the cloud-native container platform integration method provided by the above methods. The method includes: determining the operating environment of the cloud-native container platform event flow; determining a workflow template based on continuous integration and continuous deployment processes in the operating environment; deploying event triggers in a code repository based on the workflow template; and triggering the cloud-native container platform event flow using the event triggers.

[0105] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0106] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0107] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for integrating a cloud-native container platform, characterized in that, include: Determine the runtime environment for the event stream of the cloud-native container platform; In the aforementioned operating environment, workflow templates are determined based on continuous integration and continuous deployment processes; Based on the workflow template, deploying an event trigger in the code repository includes: deploying a reverse push interface webhook in the code repository; determining the EventBus component and Sensor component based on the address of the webhook; obtaining the event source (eventsource) based on the EventBus component and forwarding the event source to the Sensor; and creating the event trigger based on the Sensor component and the event source. The event trigger is used to trigger the cloud-native container platform event stream.

2. The cloud-native container platform integration method according to claim 1, characterized in that, The determination of the runtime environment for the cloud-native container platform event flow includes: Create a Kubernetes cluster for container orchestration engines, which includes control nodes and worker nodes; The container-local workflow engine argo-workflow is deployed using the package management tool Helm and an offline image deployment mode. The argo command line is deployed using binary mode, and the argo-event engine is deployed using Helm. The argo-workflow and the argo-event engine use the same command space.

3. The cloud-native container platform integration method according to claim 1, characterized in that, In the aforementioned operating environment, the workflow template is determined based on continuous integration and continuous deployment processes, including: Create an execution step template based on the continuous integration and continuous deployment process, and obtain the storage status of the continuous integration and continuous deployment process; The execution step template is output in container pod mode to form the workflow template.

4. The cloud-native container platform integration method according to claim 1, characterized in that, After deploying event triggers in the code repository based on the workflow template, the process further includes: Create an event; Based on the event, the event trigger automatically triggers the cloud-native container platform event stream.

5. The cloud-native container platform integration method according to claim 1, characterized in that, The step of triggering the cloud-native container platform event stream using the event trigger includes: Execute push and merge operations in the code repository, and obtain pod runtime logs for the continuous integration and continuous deployment process through the event triggers; The runtime status of the cloud-native container platform event stream is obtained based on the pod runtime logs.

6. A cloud-native container platform integration system, characterized in that, include: The first determination module is used to determine the runtime environment of the cloud-native container platform event stream; The second determining module is used to determine a workflow template based on the continuous integration and continuous deployment processes in the operating environment. The deployment module is used to deploy event triggers in the code repository based on the workflow template, including: deploying a reverse push interface webhook in the code repository; determining the EventBus component and Sensor component based on the address of the webhook; obtaining the event source eventsource based on the EventBus component and forwarding the event source to the Sensor; and creating the event trigger based on the Sensor component and the eventsource. The triggering module is used to trigger the event stream of the cloud-native container platform using the event trigger.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the cloud-native container platform integration method as described in any one of claims 1 to 5.

8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the cloud-native container platform integration method as described in any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the cloud-native container platform integration method as described in any one of claims 1 to 5.

Images