Network routing configuration methods, devices, electronic equipment and storage media

Abstract

This application provides a network routing configuration method, apparatus, electronic device, and storage medium. The method includes: invoking an external service listener to detect changes in a target external service; obtaining external service change information corresponding to the target external service; and synchronizing the external service change information to a service metadata registry, so that after the SD-WAN service controller detects the external service change information from the service metadata registry, the SD-WAN management center configures the network route for the target external service based on the external service change information. This application can achieve dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within Kubernetes change.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a network routing configuration method, apparatus, electronic device and storage medium. Background Technology

[0002] Kubernetes is a container orchestration engine that can schedule the computing power of multiple hosts, and perform reasonable orchestration and scheduling of applications at the smallest unit of POD to ensure application elasticity and high availability.

[0003] SD-WAN (Software-Defined Wide Area Network) is a service that applies SDN technology to wide area network (WAN) scenarios. This service is used to connect enterprise networks, data centers, Internet applications, and cloud services over a wide geographical area.

[0004] Mainstream SD-WAN solutions in the industry provide visual interfaces for manual configuration of service routing rules and policies. They also typically offer API interfaces or XML configurations, allowing users to flexibly implement dynamic routing configurations for CPE (Customer Premise Equipment) / POP (Point of Production) nodes. In Kubernetes, services are provided via services, but these services primarily serve business systems within the Kubernetes cluster. Providing services outside the cluster is generally done through Ingress or Node Ports. Current SD-WAN routing configuration solutions lack business-awareness capabilities. Summary of the Invention

[0005] This application provides a network routing configuration method, apparatus, electronic device, and storage medium to address the problem that SD-WAN routing configuration schemes in related technologies lack the ability to perceive services.

[0006] To solve the above-mentioned technical problems, the embodiments of this application are implemented as follows:

[0007] In a first aspect, embodiments of this application provide a network routing configuration method applied to a Kubernetes cluster, the method comprising:

[0008] The external service listener is invoked to detect changes to the target external service.

[0009] Obtain the external service change information corresponding to the target external service;

[0010] The external service change information is synchronized to the service metadata registry center so that after the SD-WAN service controller listens to the external service change information in the service metadata registry center, the SD-WAN management and control center configures the network route of the target external service according to the external service change information.

[0011] Optionally, obtaining the external service change information corresponding to the target external service includes:

[0012] Obtain the metadata information of the target's external services;

[0013] The metadata information is parsed to determine the external service change information of the target external service.

[0014] Optionally, the target external service is at least one of Ingress service and Node Port service.

[0015] Secondly, embodiments of this application provide a network routing configuration method applied to an SD-WAN management and control center, the method comprising:

[0016] Obtain the external service change information of the target external service from the service metadata registry center monitored by the SD-WAN service controller; the external service change information is monitored and synchronized to the service metadata registry center by the external service listener in the Kubernetes cluster.

[0017] Configure the network route for the target external service based on the external service change information.

[0018] Optionally, configuring the network route for the target external service based on the external service change information includes:

[0019] Based on the external service change information, determine the target application type corresponding to the target external service;

[0020] Based on the pre-configured correspondence between application types and network routes, determine the network route corresponding to the target's external service;

[0021] Configure the network routing for the target's external services.

[0022] Thirdly, embodiments of this application provide a network routing configuration device applied to a Kubernetes cluster, the device comprising:

[0023] The target external service listening module is used to call the external service listener to detect changes in the target external service;

[0024] The service change information acquisition module is used to acquire the external service change information corresponding to the target external service;

[0025] The first network routing configuration module is used to synchronize the external service change information to the service metadata registry center, so that after the SD-WAN service controller listens to the external service change information of the service metadata registry center, the SD-WAN management and control center configures the network route of the target external service according to the external service change information.

[0026] Optionally, the service change information acquisition module includes:

[0027] Metadata information acquisition unit, used to acquire metadata information of the target's external services;

[0028] The service change information determination unit is used to parse the metadata information and determine the external service change information of the target external service.

[0029] Optionally, the target external service is at least one of Ingress service and Node Port service.

[0030] Fourthly, embodiments of this application provide a network routing configuration device applied in an SD-WAN management center, the device comprising:

[0031] The external service change information acquisition module is used to acquire the external service change information of the target external service in the service metadata registry center monitored by the SD-WAN service controller; the external service change information is monitored by the external service listener in the Kubernetes cluster and synchronized to the service metadata registry center.

[0032] The second network routing configuration module is used to configure the network routing of the target external service based on the external service change information.

[0033] Optionally, the second network routing configuration module includes:

[0034] The application type determination unit is used to determine the target application type corresponding to the target external service based on the external service change information.

[0035] The network routing determination unit is used to determine the network route corresponding to the target's external service based on the pre-configured correspondence between application types and network routes.

[0036] The network routing configuration unit is used to configure the network routing for the target's external services.

[0037] Fifthly, embodiments of this application provide an electronic device, including:

[0038] A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the network routing configuration method described in any of the preceding claims.

[0039] Sixthly, embodiments of this application provide a readable storage medium that, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the network routing configuration method described in any of the preceding claims.

[0040] In this embodiment, an external service listener is invoked to detect changes in the target external service, obtain the corresponding external service change information, and synchronize the external service change information to the service metadata registry. After the SD-WAN service controller detects the external service change information from the service metadata registry, the SD-WAN management center configures the network route for the target external service based on the external service change information. This embodiment, by listening to the external services (Ingress service and Node Port service) of the Kubernetes cluster, can synchronize routing rules to the SD-WAN controller when external services within the Kubernetes cluster change. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within Kubernetes change.

[0041] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

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

[0043] Figure 1 A flowchart illustrating the steps of a network routing configuration method provided in this application embodiment;

[0044] Figure 2 A schematic diagram of a routing configuration architecture provided in an embodiment of this application;

[0045] Figure 3 A flowchart illustrating the steps of another network routing configuration method provided in this application embodiment;

[0046] Figure 4 This is a schematic diagram of the structure of a network routing configuration device provided in an embodiment of this application;

[0047] Figure 5 This is a schematic diagram of another network routing configuration device provided in an embodiment of this application;

[0048] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0050] Reference Figure 1 The diagram illustrates a flowchart of a network routing configuration method provided in an embodiment of this application, which can be applied to Kubernetes clusters. Figure 1 As shown, the network routing configuration method may include the following steps:

[0051] Step 101: Call the external service listener to detect changes in the target external service.

[0052] The embodiments of this application can be applied to scenarios where SD-WAN is used to dynamically detect and configure Kubernetes services when external services within a Kubernetes cluster change.

[0053] The embodiments of this application can be applied to Kubernetes clusters. Kubernetes (K8s for short) is an open-source application used to manage containerized applications on multiple hosts in a cloud platform. The goal of Kubernetes is to make deploying containerized applications simple and efficient. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance.

[0054] External service listeners are listeners set up within a Kubernetes cluster and can be used to listen for external services (Ingress service and Node Port service) of the Kubernetes cluster.

[0055] In practice, after the Kubernetes cluster starts working, an external service listener can be started within the Kubernetes cluster to monitor external services. If a change occurs in an external service, the external service listener can detect the change in the target external service within the Kubernetes cluster.

[0056] After the external service listener detects a change in the target external service, step 102 is executed.

[0057] Step 102: Obtain the external service change information corresponding to the target external service.

[0058] Information on changes to external services can include information such as the application type of the application to which the target external service belongs. In this example, the application type can be: video application type, text application type, and voice application type, etc.

[0059] After the external service listener detects a change in the target external service, it can obtain the corresponding external service change information.

[0060] In practical implementation, when deploying applications within a Kubernetes cluster, the application type can be specified. Specifically, Kubernetes deploys applications via YAML configuration files. During deployment, the corresponding service YAML file contains service metadata information, indicating the application type (e.g., video application, audio application, text application, etc.). An external service listener runs in Kubernetes, its function being to monitor for newly added / modified / deleted Node Port Services and Ingress Services within the Kubernetes cluster. After detecting a change in the target external service, it can obtain and parse the metadata information to determine the change details.

[0061] After obtaining the external service change information corresponding to the target external service, proceed to step 103.

[0062] Step 103: Synchronize the external service change information to the service metadata registry center, so that after the SD-WAN service controller listens to the external service change information of the service metadata registry center, the SD-WAN management and control center configures the network route of the target external service according to the external service change information.

[0063] After obtaining the external service change information corresponding to the target external service, the external service change information can be passed to the service metadata registry. After the SD-WAN service controller listens to the external service change information of the service metadata registry, the SD-WAN management and control center configures the network route of the target external service according to the external service change information.

[0064] This application embodiment monitors the external services (Ingress service and Node Port service) of the Kubernetes cluster. When the external services within the Kubernetes cluster change, the routing rules are synchronized to the SD-WAN controller. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within the Kubernetes cluster change.

[0065] The above implementation process can be combined with Figure 2 The following is a detailed description.

[0066] like Figure 2 As shown, the edge nodes integrate the functionality of the SD-WAN CPE, consolidating it within the edge node itself. SD-WAN provides a unified management and control center, which can control the routing rules and network policies of each CPE and POP point. The SD-WAN management and control center is typically located in the central cloud, managing all CPEs and POP points. Edge services select different WAN exits based on the QoS (Quality of Service) requirements of different application types. At the intermediate SD-WAN POP point, the routing direction of network packets is determined according to routing rules and policies. An external service listener is deployed in the central cloud Kubernetes cluster to monitor changes to the Ingress service and Node Port service, and the change information is pushed to the external service metadata registry. The SD-WAN service controller module listens for changes in the service metadata registry, obtains the service metadata, and calls the SD-WAN API based on the metadata information. The SD-WAN management and control center is responsible for updating the routing rules of each CPE and POP point.

[0067] In the overall architecture diagram of this embodiment, the newly added modules are: a service metadata registry center and an external service monitoring service. Simultaneously, the existing SD-WAN service controller needs to be modified to synchronize service metadata to the SD-WAN controller. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within K8S change.

[0068] In practical applications, when edge nodes need to use the central cloud Kubernetes service, the SD-WAN CPE and the intermediate POP nodes automatically select the network route suitable for the business QoS according to the pre-configured routing policy.

[0069] The network routing configuration method provided in this application embodiment listens for changes to the target external service by calling an external service listener, obtains the corresponding external service change information, and synchronizes the external service change information to the service metadata registry. After the SD-WAN service controller listens for the external service change information from the service metadata registry, the SD-WAN management center configures the network route for the target external service based on the external service change information. This application embodiment, by listening to the external services (Ingress service and Node Port service) of the Kubernetes cluster, can synchronize routing rules to the SD-WAN controller when external services within the Kubernetes cluster change. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within Kubernetes change.

[0070] Reference Figure 3 This illustration shows a flowchart of another network routing configuration method provided in an embodiment of this application, which can be applied to an SD-WAN management center. Figure 3 As shown, the network routing configuration method may include the following steps:

[0071] Step 301: Obtain the external service change information of the target external service in the service metadata registry center listened to by the SD-WAN service controller; the external service change information is listened to and synchronized to the service metadata registry center by the external service listener in the Kubernetes cluster.

[0072] The embodiments of this application can be applied to SD-WAN management and control centers, that is, the executing entity is the SD-WAN management and control center.

[0073] In a specific implementation, the SD-WAN service controller can listen to the external service change information of the target external service in the service metadata registry. The external service change information is listened to by the external service listener in the Kubernetes cluster and synchronized to the service metadata registry.

[0074] In practical applications, an external service listener runs in Kubernetes. Its function is to monitor the addition, modification, and deletion of Node Port Services and Ingress Services in the Kubernetes cluster. The external service listener module synchronizes the external service change information to the service metadata registry. The SD-WAN service controller listens for service change information from the service metadata registry.

[0075] After obtaining the external service change information of the target external service in the service metadata registry center listened to by the SD-WAN service controller, step 302 is executed.

[0076] Step 302: Configure the network route for the target external service based on the external service change information.

[0077] After obtaining the external service change information of the target external service from the service metadata registry center monitored by the SD-WAN service controller, the network routing of the target external service can be configured based on the external service change information. This implementation process can be described in detail below with reference to the specific implementation method.

[0078] In one specific implementation of this application, step 302 may include:

[0079] Sub-step S1: Based on the external service change information, determine the target application type corresponding to the target external service.

[0080] In this embodiment, after obtaining the external service change information of the target external service, the target application type corresponding to the target external service can be determined based on the external service change information.

[0081] After determining the target application type corresponding to the target external service based on the external service change information, proceed with sub-step S2.

[0082] Sub-step S2: Determine the network route corresponding to the target's external service based on the pre-configured correspondence between application types and network routes.

[0083] After determining the target application type corresponding to the target external service based on the external service change information, the network route corresponding to the target external service can be determined according to the pre-configured correspondence between application types and network routes.

[0084] Sub-step S3: Configure the network routing for the target's external services.

[0085] After determining the network route corresponding to the target's external service, the network route of the target's external service can be configured, that is, the network route corresponding to the determined target's external service is configured to the target's external service.

[0086] The network routing configuration method provided in this application obtains external service change information of the target external service from the service metadata registry, which is monitored by the SD-WAN service controller. This external service change information is monitored by the external service listener within the Kubernetes cluster and synchronized to the service metadata registry. Based on this external service change information, the network route for the target external service is configured. By monitoring the external services (Ingress service and Node Port service) of the Kubernetes cluster, this application embodiment can synchronize routing rules to the SD-WAN controller when changes occur in the external services within the Kubernetes cluster. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when changes occur in services within Kubernetes.

[0087] Reference Figure 4 This illustration shows a structural diagram of a network routing configuration device provided in an embodiment of this application. This network routing configuration device can be applied to a Kubernetes cluster. Figure 4 As shown, the network routing configuration device may include the following modules:

[0088] The target external service listening module 410 is used to call the external service listener to listen for changes in the target external service;

[0089] The service change information acquisition module 420 is used to acquire the external service change information corresponding to the target external service;

[0090] The first network routing configuration module 430 is used to synchronize the external service change information to the service metadata registration center, so that after the SD-WAN service controller listens to the external service change information of the service metadata registration center, the SD-WAN management and control center configures the network route of the target external service according to the external service change information.

[0091] Optionally, the service change information acquisition module includes:

[0092] Metadata information acquisition unit, used to acquire metadata information of the target's external services;

[0093] The service change information determination unit is used to parse the metadata information and determine the external service change information of the target external service.

[0094] Optionally, the target external service is at least one of Ingress service and Node Port service.

[0095] The network routing configuration device provided in this application embodiment listens for changes to target external services by invoking an external service listener, obtains the corresponding external service change information, and synchronizes the external service change information to the service metadata registry. After the SD-WAN service controller listens for the external service change information from the service metadata registry, the SD-WAN management center configures the network route for the target external service based on the external service change information. This application embodiment, by listening to the external services (Ingress service and Node Port service) of the Kubernetes cluster, can synchronize routing rules to the SD-WAN controller when external services within the Kubernetes cluster change. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when services within Kubernetes change.

[0096] Reference Figure 5 This illustration shows a schematic diagram of another network routing configuration device provided in an embodiment of this application, which can be applied to an SD-WAN management center. Figure 5 As shown, the network routing configuration device may include the following modules:

[0097] The external service change information acquisition module 510 is used to acquire the external service change information of the target external service in the service metadata registry center listened to by the SD-WAN service controller; the external service change information is listened to and synchronized to the service metadata registry center by the external service listener in the Kubernetes cluster.

[0098] The second network routing configuration module 520 is used to configure the network routing of the target external service according to the external service change information.

[0099] Optionally, the second network routing configuration module includes:

[0100] The application type determination unit is used to determine the target application type corresponding to the target external service based on the external service change information.

[0101] The network routing determination unit is used to determine the network route corresponding to the target's external service based on the pre-configured correspondence between application types and network routes.

[0102] The network routing configuration unit is used to configure the network routing for the target's external services.

[0103] The network routing configuration device provided in this application embodiment obtains external service change information of the target external service from the service metadata registry center monitored by the SD-WAN service controller. This external service change information is monitored by the external service listener within the Kubernetes cluster and synchronized to the service metadata registry center. Based on this external service change information, the network route for the target external service is configured. By monitoring the external services (Ingress service and Node Port service) of the Kubernetes cluster, this application embodiment can synchronize routing rules to the SD-WAN controller when changes occur in the external services within the Kubernetes cluster. This enables dynamic awareness and dynamic routing configuration of Kubernetes services through SD-WAN when changes occur in services within Kubernetes.

[0104] Additionally, this application 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 computer program, when executed by the processor, implements the above-described network routing configuration method.

[0105] Figure 6 A schematic diagram of the structure of an electronic device 600 according to an embodiment of the present invention is shown. Figure 6 As shown, the electronic device 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to computer program instructions stored in read-only memory (ROM) 602 or loaded from storage unit 608 into random access memory (RAM) 603. The RAM 603 may also store various programs and data required for the operation of the electronic device 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0106] Multiple components in electronic device 600 are connected to I / O interface 605, including: input unit 606, such as keyboard, mouse, microphone, etc.; output unit 607, such as various types of displays, speakers, etc.; storage unit 608, such as disk, optical disk, etc.; and communication unit 609, such as network card, modem, wireless transceiver, etc. Communication unit 609 allows electronic device 600 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0107] The various processes and handling described above can be executed by processing unit 601. For example, the methods of any of the above embodiments can be implemented as computer software programs tangibly contained in a computer-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 600 via ROM 602 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by CPU 601, one or more actions of the methods described above can be performed.

[0108] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described network routing configuration method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0109] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, 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 is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0111] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0112] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0113] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0114] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0115] 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 units can be selected to achieve the purpose of this embodiment according to actual needs.

[0116] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0117] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion 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 this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0118] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A network routing configuration method applied to a Kubernetes cluster, characterized in that, The method includes: The external service listener is invoked to detect changes to the target external service. Obtain the external service change information corresponding to the target external service; the external service change information includes the application type of the application to which the target external service belongs; The external service change information is synchronized to the service metadata registry center. After the SD-WAN service controller detects the external service change information from the service metadata registry center, the SD-WAN management center configures the network route for the target external service based on the external service change information. The network route for the target external service is obtained based on the pre-configured correspondence between the application type and the network route.

2. The method according to claim 1, characterized in that, The step of obtaining the external service change information corresponding to the target external service includes: Obtain the metadata information of the target's external services; The metadata information is parsed to determine the external service change information of the target external service.

3. The method according to claim 1 or 2, characterized in that, The target external service is at least one of Ingress service and Node Port service.

4. A network routing configuration method, applied to an SD-WAN management and control center, characterized in that, The method includes: Obtain the external service change information of the target external service from the service metadata registry center monitored by the SD-WAN service controller; the external service change information includes the application type of the application to which the target external service belongs; the external service change information is monitored and synchronized to the service metadata registry center by the external service listener in the Kubernetes cluster. Based on the external service change information, configure the network route for the target external service. The network route for the target external service is obtained based on the pre-configured correspondence between the application type and the network route.

5. The method according to claim 4, characterized in that, The step of configuring the network route for the target external service based on the external service change information includes: Based on the external service change information, determine the target application type corresponding to the target external service; Based on the pre-configured correspondence between application types and network routes, determine the network route corresponding to the target's external service; Configure the network routing for the target's external services.

6. A network routing configuration device, applied to a Kubernetes cluster, characterized in that, The device includes: The target external service listening module is used to call the external service listener to detect changes in the target external service; The service change information acquisition module is used to acquire the external service change information corresponding to the target external service; the external service change information includes the application type of the application to which the target external service belongs; The first network routing configuration module is used to synchronize the external service change information to the service metadata registry center. After the SD-WAN service controller listens to the external service change information of the service metadata registry center, the SD-WAN management and control center configures the network route of the target external service according to the external service change information. The network route of the target external service is obtained based on the pre-configured correspondence between the application type and the network route.

7. The apparatus according to claim 6, characterized in that, The service change information acquisition module includes: Metadata information acquisition unit, used to acquire metadata information of the target's external services; The service change information determination unit is used to parse the metadata information and determine the external service change information of the target external service.

8. The apparatus according to claim 6 or 7, characterized in that, The target external service is at least one of Ingress service and Node Port service.

9. A network routing configuration device, applied in an SD-WAN management and control center, characterized in that, The device includes: The external service change information acquisition module is used to acquire external service change information of a target external service in the service metadata registry center monitored by the SD-WAN service controller; the external service change information includes the application type of the application to which the target external service belongs; the external service change information is monitored and synchronized to the service metadata registry center by the external service listener in the Kubernetes cluster. The second network routing configuration module is used to configure the network route of the target external service according to the external service change information. The network route of the target external service is obtained based on the pre-configured correspondence between the application type and the network route.

10. The apparatus according to claim 9, characterized in that, The second network routing configuration module includes: The application type determination unit is used to determine the target application type corresponding to the target external service based on the external service change information. The network routing determination unit is used to determine the network route corresponding to the target's external service based on the pre-configured correspondence between application types and network routes. The network routing configuration unit is used to configure the network routing for the target's external services.

11. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the network routing configuration method as described in any one of claims 1 to 5.

12. A readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the network routing configuration method according to any one of claims 1 to 5.

Images