CN115480877A - External exposure method and device of application service in multi-cluster environment - Google Patents

Abstract

The invention discloses an external exposure method and device of application services in a multi-cluster environment, and relates to the technical field of computers. One embodiment of the method comprises: in response to the application deployment operation, creating customized resources under the application namespace, wherein the customized resources comprise service information exposed by the application to the outside; responding to the monitored creation event of the customized resource, and generating an access domain name of the application service according to the service information; and registering the access domain name into a domain name resolver, and storing the access domain name into a customized resource so as to expose the application service to the outside by accessing the domain name. According to the embodiment, after the application is deployed in the multi-cluster environment, the access domain name exposed to the outside is automatically generated for the application service, the deployed application can be accessed outside the cluster through the access domain name, the condition that the service cannot be accessed due to single-point failure is avoided, and the application service can be accessed more flexibly, conveniently and efficiently.

Description

Method and device for external exposure of application services in multi-cluster environment

technical field

The present invention relates to the field of computer technology, in particular to a method and device for externally exposing application services in a multi-cluster environment.

Background technique

Applications deployed on a Kubernetes cluster generally run on the private network of the Kubernetes cluster, so it is necessary to provide a service exposure method to receive external access. At present, there are generally the following ways to provide service access outside the Kubernetes cluster:

1. Based on the NodePort (node port) and LoadBalancer (load balancing) services of the Kubernetes cluster, this method exposes the service through the IP address + port;

2. With the help of a third-party Ingress (an API interface object that manages external access to services in the cluster) controller, the service is exposed through the domain name.

In the course of realizing the present invention, the inventor finds that there are at least the following problems in the prior art:

For the two service exposure methods based on NodePort and LoadBalancer, users access the service through IP address + port, which may cause a single point of failure, resulting in inability to access the service, and the LoadBalancer method is generally only provided by cloud vendors. With the help of Ingress to provide service exposure, you need to apply for a generic domain name for each Kubernetes cluster, and a generic domain name can only be resolved to one Kubernetes cluster, so it cannot be applied to multi-cluster scenarios.

Contents of the invention

In view of this, the embodiments of the present invention provide a method and device for externally exposing application services in a multi-cluster environment, which can automatically generate externally exposed access domain names for application services after deploying applications in a multi-Kubernetes cluster environment, and can be used outside the Kubernetes cluster By accessing the domain name to access the deployed application, it avoids the situation that the service cannot be accessed due to a single point of failure, making the access to the application service more flexible, convenient and efficient.

In order to achieve the above purpose, according to an aspect of the embodiments of the present invention, a method for externally exposing application services in a multi-cluster environment is provided, including:

In response to an application deployment operation, create a custom resource under the namespace of the application, where the custom resource includes service information exposed by the application;

In response to listening to the creation event of the custom resource, generate an access domain name of the application service according to the service information;

The access domain name is registered in the domain name resolver, and the access domain name is saved in the customized resource, so that the application service is exposed externally through the access domain name.

Optionally, creating a custom resource under the namespace of the application includes: adding a custom resource configuration file under the namespace of the application, the custom resource configuration file includes service information required to generate the custom resource; according to the Create a custom resource based on the service information exposed by the application and the custom resource configuration file.

Optionally, the service information includes the service name, the node port information corresponding to the service, the namespace information of the service in the cluster, and the cluster identifier; generating the access domain name of the application service according to the service information includes: name, the namespace information of the service in the cluster, the cluster identifier, the generic domain name suffix, and the node port information corresponding to the service are spliced according to the set domain name format to generate the access domain name of the application service, wherein the generic domain name suffix is the same as The suffix of the generic domain name associated with the domain name resolver.

Optionally, registering the access domain name in the domain name resolver includes: registering the mapping relationship between the access address and node port information of the cluster where the service is deployed and the access domain name in accordance with the cluster ID and the customized resource ID as tags to register in the domain name resolver device.

Optionally, saving the access domain name in the customized resource includes: saving the access domain name and the service information in a status field of the customized resource.

Optionally, the method further includes: deleting the custom resource in response to listening to the deletion event of the custom resource, and searching the domain name resolver for information related to the custom resource according to the cluster identifier and the custom resource identifier and delete the mapping relationship record.

According to another aspect of the embodiments of the present invention, a device for externally exposing application services in a multi-cluster environment is provided, including:

A custom resource creation module, configured to create a custom resource under the namespace of the application in response to an application deployment operation, where the custom resource includes service information exposed by the application;

An access domain name generating module, configured to generate an access domain name of the application service according to the service information in response to listening to the creation event of the custom resource, and register the access domain name in the domain name resolver;

The access domain name issuing module is configured to register the access domain name in a domain name resolver, and store the access domain name in the customized resource, so as to expose the application service to the outside through the access domain name.

Optionally, the custom resource creation module is further configured to: add a custom resource configuration file under the namespace of the application, the custom resource configuration file includes service information required to generate the custom resource; The service information and the custom resource configuration file create a custom resource.

Optionally, the service information includes the service name, the node port information corresponding to the service, the namespace information of the service in the cluster, and the cluster identifier; the access domain name generation module is also used to: use the service name, service Namespace information belonging to the cluster, cluster identifier, generic domain name suffix, and node port information corresponding to the service are spliced according to the set domain name format to generate an access domain name for the application service, wherein the generic domain name suffix is resolved with the domain name The suffix of the wildcard domain name associated with the server.

Optionally, the access domain name generating module is further configured to: register the mapping relationship between the access address and node port information of the cluster where the service is deployed and the access domain name in the domain name resolver according to the cluster ID and the customized resource ID as tags.

Optionally, the access domain name publishing module is further configured to: save the access domain name and the service information in the status field of the customized resource.

Optionally, it also includes a domain name deletion module, configured to: delete the custom resource in response to hearing the deletion event of the custom resource, and search the domain name resolver for the domain name resolver according to the cluster identifier and the customized resource identifier Customize resource-related mapping relationship records, and delete the mapping relationship records.

According to yet another aspect of the embodiments of the present invention, there is provided an externally exposed electronic device for application services in a multi-cluster environment, including: one or more processors; a storage device for storing one or more programs, when the One or more programs are executed by the one or more processors, so that the one or more processors implement the method for externally exposing application services in a multi-cluster environment provided by the embodiments of the present invention.

According to yet another aspect of the embodiments of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the external communication of application services in a multi-cluster environment provided by the embodiments of the present invention is realized. exposure method.

An embodiment of the above invention has the following advantages or beneficial effects: by responding to the application deployment operation, creating a custom resource under the namespace of the application, the custom resource includes the service information exposed by the application; in response to listening to the creation event of the custom resource , generate the access domain name of the application service according to the service information; register the access domain name in the domain name resolver, and save the access domain name in the customized resource, so as to expose the technical solution of the application service through the access domain name, and maintain it through the customized resource Apply the service information exposed to the outside world, listen to customized resources to generate a domain name according to the service information, register the domain name in the domain name resolver, and resolve the domain name to the corresponding cluster, realizing access to the cluster through the domain name outside the Kubernetes cluster application services. After the application is deployed in a multi-Kubernetes cluster environment, the access domain name exposed to the outside world is automatically generated for the application service, and the deployed application can be accessed through the access domain name outside the Kubernetes cluster, avoiding the situation that the service cannot be accessed due to a single point of failure. Access to application services is more flexible, convenient and efficient.

The further effects of the above-mentioned non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used to better understand the present invention, and do not constitute improper limitations to the present invention. in:

FIG. 1 is a schematic diagram of main steps of a method for externally exposing application services in a multi-cluster environment according to an embodiment of the present invention;

Fig. 2 is a schematic diagram of the process of generating an external exposure method of an application service according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a domain name-based application service access flow in an embodiment of the present invention;

4 is a schematic diagram of main modules of an externally exposed device for application services in a multi-cluster environment according to an embodiment of the present invention;

FIG. 5 is an exemplary system architecture diagram to which the embodiment of the present invention can be applied;

Fig. 6 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

detailed description

Exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding, and they should be regarded as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The acquisition, storage, use, and processing of data in the technical solution of the present invention all comply with the relevant provisions of national laws and regulations.

In order to solve the technical problems existing in the prior art, the embodiment of the present invention provides a method for externally exposing application services in a multi-cluster environment. After the application is deployed in a multi-Kubernetes cluster environment, an externally exposed access domain name is automatically generated for the application service. Make it possible to access the deployed application through the access domain name outside the Kubernetes cluster. The technical scheme of the present invention is applicable to an environment with one or more Kubernetes clusters, and the applications deployed on each cluster expose access methods through domain names. The application mentioned in the technical solution of the present invention has provided NodePort (node port) type service by default.

In the introduction of the embodiments of the present invention, the technical terms involved and their interpretations are as follows:

Kubernetes: A container orchestration tool open sourced by Google, currently popular in the field of container orchestration, abbreviated as k8s;

CRD: The full name is Custom Resource Definition, which is a native resource type built into Kubernetes, which allows users to add a custom API resource type in Kubernetes, namely: the definition of custom resources;

CR: The full name is Custom Resource, which is a specific resource customized according to CRD;

Generic domain name: Use the wildcard * (asterisk) as a sub-domain name, so that all sub-domain names point to the same IP address. For example: *.demo.com is resolved to 111.1.1.1, then all domain names ending with .demo.com will be resolved to 111.1.1.1;

Pod: The smallest unit managed by Kubernetes. To run a program, it must be deployed in a container, and the container must exist in the Pod. Pod can be considered as the package of containers, and one or more containers can exist in a Pod;

Service: An abstract method that exposes applications running on a set of Pods as network services, and forwards requests from proxy clients to one of the backend set of Pods.

FIG. 1 is a schematic diagram of main steps of a method for externally exposing application services in a multi-cluster environment according to an embodiment of the present invention. As shown in FIG. 1 , the method for externally exposing application services in a multi-cluster environment according to the embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: In response to an application deployment operation, create a custom resource under the namespace of the application, where the custom resource includes service information exposed by the application. When it is necessary to deploy an application in a Kubernetes cluster, under the namespace namespace of the application, create a custom resource CR (a custom resource in k8s) for exposing the service access method, and record what the application needs to expose in the custom resource CR The service information of the node port NodePort type. The service information includes at least the service name, the node port information NodePort corresponding to the service, the namespace information namespace to which the service belongs in the cluster, and the cluster identifier clusterId.

According to an embodiment of the present invention, creating a custom resource under the namespace of the application may specifically include: adding a custom resource configuration file under the namespace of the application, the custom resource configuration file includes service information required to generate the custom resource; Create custom resources using exposed service information and custom resource configuration files. In the embodiment of the present invention, the custom resource configuration file is, for example, a CRD, which defines the parameters and parameter forms required for building a custom resource CR, and how to generate the relevant rules of the custom resource CR according to these parameters, and so on. In the embodiment of the present invention, a CRD for service exposure can be pre-defined, and the definition CRD (similar to a table structure) of this custom resource can be added to the Kubernetes cluster, so that this type of custom resource can be created . The specification of CRD in Kubernetes includes fields such as apiVersion, kind, metadata, spec, status, etc. The spec field describes the type, name, version number of the resource to be customized and the specific data structure involved. Define an array in the spec field of the CRD, and record service information in the array. Each service information includes at least four elements: service name name, node port information NodePort, namespace information namespace, and cluster identifier clusterId. An array is defined in the status field of the CRD, and the four elements of the service and the generated access domain name are recorded in the array.

Step S102: In response to listening to the custom resource creation event, generate an access domain name of the application service according to the service information. In the embodiment of the present invention, a domain name controller is deployed in each Kubernetes cluster, which is used to monitor the operation event of the custom resource CR, and generate the access domain name associated with the CR according to the service information in the CR, and the generated The access domain name is registered in the domain name resolver. The domain name resolver is used to store and resolve domain names, and can record domain name information and resolve domain names. Access requests through domain names can be routed to corresponding application services through domain name resolvers. In the embodiment of the present invention, the operation event of the customized resource is monitored through the domain name controller deployed in the cluster. When the application is deployed in the cluster, it will listen to the creation event of the custom resource. Correspondingly, in other scenarios, the update event or delete event of the custom resource can also be monitored, and so on.

According to one embodiment of the present invention, generating the access domain name of the application service according to the service information may specifically include: the service name, the namespace information of the service in the cluster, the cluster identifier, the suffix of the generic domain name, and the node port information corresponding to the service , splicing according to the set domain name format to generate the access domain name of the application service, wherein the generic domain name suffix is the suffix of the generic domain name associated with the domain name resolver. Among them, the suffix of the generic domain name refers to the part after * in the generic domain name. In the embodiment of the present invention, in order to deploy applications in multiple clusters, all requests for accessing the same application can be forwarded to the domain name resolver associated with the generic domain name through an externally resolvable generic domain name, and passed The domain name resolver forwards the request to the corresponding cluster.

In an embodiment of the present invention, the preset domain name format is, for example: name.namespace.clusterId.<Global domain name suffix>:NodePort format. When generating the access domain name of the application service based on the service information, it is specifically generated by concatenating the service name name, namespace information namespace, cluster identifier clusterId, generic domain name suffix, and node port information NodePort according to the domain name format.

Step S103: Register the access domain name in the domain name resolver, and save the access domain name in a custom resource, so as to expose the application service to the outside through the access domain name. After the access domain name is generated, the access domain name is also written back to the custom resource CR, so that the user can obtain the access domain name through the CR, and expose the application service to the outside through the access domain name.

According to an embodiment of the present invention, when registering the access domain name in the domain name resolver, it may specifically include: mapping the access address and node port information of the cluster where the service is deployed to the access domain name, according to the cluster ID and the custom resource ID Register the token with the domain name resolver. Wherein, the access address of the cluster where the service is deployed is the IP address of the cluster, and the customized resource identifier is, for example, the name of the customized resource. In the embodiment of the present invention, for example, the mapping relationship between the IP+NodePort of the current Kubernetes cluster and the access domain name is registered or updated in the domain name resolver according to the cluster identifier clusterId+CR name.

According to an embodiment of the present invention, when saving the access domain name in the customized resource, it may specifically save the access domain name and service information in the status field of the customized resource, that is, save the access domain name and service information in the status field of the CR.

According to one of the embodiments of the present invention, it may also include: in response to listening to the deletion event of the custom resource, delete the custom resource, and search the mapping relationship related to the custom resource from the domain name resolver according to the cluster ID and the custom resource ID record, and delete the mapping relationship record. When the domain name controller deployed in the cluster monitors the deletion event of the custom resource, it will directly delete the custom resource, and find information such as the access domain name related to the custom resource from the domain name resolver, and delete the corresponding record.

According to the embodiment of the present invention, if an update event of a customized resource is monitored, the access domain name of the application service is regenerated according to the service information corresponding to the update event, and the newly generated access domain name is used to replace the previous access domain name, and registered in In the domain name resolver; save the newly generated access domain name to the custom resource to update the custom resource.

Fig. 2 is a schematic diagram of the process of generating an external exposure mode of an application service according to an embodiment of the present invention. As shown in FIG. 2 , in the embodiment of the present invention, it is necessary to rely on an externally resolvable generic domain name, and a domain name controller is deployed in each Kubernetes cluster. A domain name resolver is deployed outside the Kubernetes cluster, and the domain name resolver can communicate with the network of each Kubernetes cluster node, and the pan-domain name resolves the domain name to the domain name resolver. Among them, the domain name controller can monitor the customized resource CR for exposing services, and generate the access domain name associated with it according to the service information in the CR, and register the access domain name to the domain name resolver. Domain name resolver, domain name storage and resolution manager, capable of recording domain name information and analyzing domain names. When deploying an application in multiple clusters, create a custom resource CR under the namespace where the application is deployed in each cluster, and record the service information that the application needs to expose in the CR. After the domain name controller of the cluster listens to the custom resource creation event, it generates the access domain name according to the service information in the CR, writes the access domain name back to the CR, and registers the access domain name to the domain name resolver. Wherein, the domain name resolver is associated with the generic domain name.

Fig. 3 is a schematic diagram of domain name-based application service access flow in an embodiment of the present invention. As shown in FIG. 3 , in one embodiment of the present invention, the user of the application service accesses the application service through a domain name + port. When accessing application services, the request is first sent to the pan domain name, and the pan domain name forwards the request to the domain name resolver, and the domain name resolver forwards the request to the corresponding Kubernetes cluster node according to the mapping relationship between the domain name and "cluster IP+NodePort". , and then forward the request to the Pod where the application is located according to the iptables rules. Among them, the communication between Pods on each node in the Kubernetes cluster can be realized with the help of Linux iptables rules.

Fig. 4 is a schematic diagram of main modules of an externally exposed device for application services in a multi-cluster environment according to an embodiment of the present invention. As shown in FIG. 4 , the device 400 for externally exposing application services in a multi-cluster environment according to the embodiment of the present invention mainly includes a customized resource creation module 401 , an access domain name generation module 402 and an access domain name publishing module 403 .

A custom resource creation module 401, configured to create a custom resource under the namespace of the application in response to an application deployment operation, where the custom resource includes service information exposed by the application;

An access domain name generating module 402, configured to generate an access domain name of the application service according to the service information in response to listening to the creation event of the custom resource;

The access domain name issuing module 403 is configured to register the access domain name in a domain name resolver, and store the access domain name in the customized resource, so as to expose the application service to the outside through the access domain name.

According to an embodiment of the present invention, the custom resource creation module 401 can also be used to: add a custom resource configuration file under the namespace of the application, the custom resource configuration file includes service information required for generating custom resources; Create a custom resource based on the service information exposed by the application and the custom resource configuration file.

According to another embodiment of the present invention, the service information includes the service name, the node port information corresponding to the service, the namespace information to which the service belongs in the cluster, and the cluster identifier; the access domain name generation module is also used to: The service name, the namespace information of the service in the cluster, the cluster identifier, the generic domain name suffix and the node port information corresponding to the service are spliced according to the set domain name format to generate the access domain name of the application service, wherein the generic domain name suffix is The suffix of the wildcard domain name associated with the domain name resolver.

According to another embodiment of the present invention, the access domain name generation module 402 can also be used to: register the mapping relationship between the access address and node port information of the cluster where the service is deployed, and the access domain name, according to the cluster ID and the customized resource ID as tags to register with the domain name in the parser.

According to yet another embodiment of the present invention, the access domain name issuing module 403 may also be configured to: save the access domain name and the service information in the status field of the customized resource.

According to yet another embodiment of the present invention, the device 400 for externally exposing application services in a multi-cluster environment in the embodiment of the present invention further includes a domain name deletion module (not shown in the figure), configured to: Deleting an event, deleting the custom resource, searching the domain name resolver for a mapping relationship record related to the custom resource according to the cluster identifier and the custom resource identifier, and deleting the mapping relationship record.

According to the technical solution of the embodiment of the present invention, by responding to the application deployment operation, creating a customized resource under the namespace of the application, the customized resource includes the service information exposed by the application; in response to listening to the creation event of the customized resource, generating The access domain name of the application service; register the access domain name in the domain name resolver, and save the access domain name in the customized resource, so as to expose the application service through the access domain name, and maintain the service exposed by the application through the customized resource Information, by listening to customized resources to generate a domain name based on service information, and registering the domain name in the domain name resolver, the domain name can be resolved to the corresponding cluster, and the application service in the cluster can be accessed through the domain name outside the Kubernetes cluster. After the application is deployed in a multi-Kubernetes cluster environment, the access domain name exposed to the outside world is automatically generated for the application service, and the deployed application can be accessed through the access domain name outside the Kubernetes cluster, avoiding the situation that the service cannot be accessed due to a single point of failure. Access to application services is more flexible, convenient and efficient.

Fig. 5 shows an exemplary system architecture 500 to which the method for externally exposing application services in a multi-cluster environment or the device for externally exposing application services in a multi-cluster environment according to embodiments of the present invention can be applied.

As shown in FIG. 5 , a system architecture 500 may include terminal devices 501 , 502 , and 503 , a network 504 and a server 505 . The network 504 is used as a medium for providing communication links between the terminal devices 501 , 502 , 503 and the server 505 . Network 504 may include various connection types, such as wires, wireless communication links, or fiber optic cables, among others.

Users can use terminal devices 501 , 502 , 503 to interact with server 505 through network 504 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 501, 502, and 503, such as data monitoring applications, domain name resolution applications, data clusters, application deployment applications, etc. (just examples).

The terminal devices 501, 502, 503 may be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers and the like.

The server 505 may be a server that provides various services, such as a background management server that provides support for application deployment operations sent by users using terminal devices 501 , 502 , and 503 (just an example). The background management server can respond to the application deployment operation on the received data such as the application service exposure request, and create a customized resource under the namespace of the application, and the customized resource includes the service information exposed by the application; Listening to the creation event of the custom resource, generating the access domain name of the application service according to the service information; registering the access domain name in the domain name resolver, and saving the access domain name in the custom resource, to pass The access domain name performs processing such as external exposure of the application service, and feeds back the processing result (for example, access domain name—just an example) to the terminal device.

It should be noted that the method for exposing application services in a multi-cluster environment provided by the embodiment of the present invention is generally executed by the server 505 , and correspondingly, the device for exposing application services in a multi-cluster environment is generally set in the server 505 .

It should be understood that the numbers of terminal devices, networks and servers in Fig. 5 are only illustrative. According to the implementation needs, there can be any number of terminal devices, networks and servers.

Referring now to FIG. 6 , it shows a schematic structural diagram of a computer system 600 suitable for implementing a terminal device or a server according to an embodiment of the present invention. The terminal device or server shown in FIG. 6 is only an example, and should not limit the functions and application scope of this embodiment of the present invention.

As shown in FIG. 6 , a computer system 600 includes a central processing unit (CPU) 601 that can be programmed according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random-access memory (RAM) 603 Instead, various appropriate actions and processes are performed. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601 , ROM 602 , and RAM 603 are connected to each other via a bus 604 . An input/output (I/O) interface 605 is also connected to the bus 604 .

The following components are connected to the I/O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 608 including a hard disk, etc. and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, optical disk, magneto-optical disk, semiconductor memory, etc. is mounted on the drive 610 as necessary so that a computer program read therefrom is installed into the storage section 608 as necessary.

In particular, according to the disclosed embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the disclosed embodiments of the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, where the computer program includes program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication portion 609 and/or installed from removable media 611 . When this computer program is executed by a central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present invention are performed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer-readable program codes are carried. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. . Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code that includes one or more logical functions for implementing specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block in the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a A combination of dedicated hardware and computer instructions.

The units or modules involved in the embodiments of the present invention may be implemented by means of software or hardware. The described units or modules can also be set in a processor, for example, it can be described as: a processor includes a customized resource creation module, an access domain name generation module and an access domain name issuance module. Wherein, the names of these units or modules do not constitute limitations on the units or modules themselves under certain circumstances. For example, the custom resource creation module can also be described as "used to respond to the application deployment operation, in the application's A module that creates custom resources under the namespace".

As another aspect, the present invention also provides a computer-readable medium. The computer-readable medium may be contained in the device described in the above embodiments, or it may exist independently without being assembled into the device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the device, the device includes: responding to an application deployment operation, creating a custom resource under the namespace of the application, The customized resource includes service information exposed by the application; in response to monitoring the creation event of the customized resource, generating an access domain name of the application service according to the service information; registering the access domain name in a domain name resolver, And save the access domain name in the customized resource, so as to expose the application service to the outside through the access domain name.

According to the technical solution of the embodiment of the present invention, by responding to the application deployment operation, creating a customized resource under the namespace of the application, the customized resource includes the service information exposed by the application; in response to listening to the creation event of the customized resource, generating The access domain name of the application service; register the access domain name in the domain name resolver, and save the access domain name in the customized resource, so as to expose the application service through the access domain name, and maintain the service exposed by the application through the customized resource Information, by listening to customized resources to generate a domain name based on service information, and registering the domain name in the domain name resolver, the domain name can be resolved to the corresponding cluster, and the application service in the cluster can be accessed through the domain name outside the Kubernetes cluster. After the application is deployed in a multi-Kubernetes cluster environment, the access domain name exposed to the outside world is automatically generated for the application service, and the deployed application can be accessed through the access domain name outside the Kubernetes cluster, avoiding the situation that the service cannot be accessed due to a single point of failure. Access to application services is more flexible, convenient and efficient.

The above specific implementation methods do not constitute a limitation to the protection scope of the present invention. It should be apparent to those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method for externally exposing application services in a multi-cluster environment, characterized in that it comprises: In response to an application deployment operation, create a custom resource under the namespace of the application, where the custom resource includes service information exposed by the application; In response to listening to the creation event of the custom resource, generate an access domain name of the application service according to the service information, and register the access domain name in the domain name resolver; The access domain name is stored in the customized resource, so as to expose the application service to the outside through the access domain name. 2. The method according to claim 1, wherein creating a custom resource under the namespace of the application comprises: Adding a custom resource configuration file under the namespace of the application, the custom resource configuration file includes service information required to generate the custom resource; Create a customized resource according to the service information exposed by the application and the customized resource configuration file. 3. The method according to claim 1, wherein the service information includes a service name, node port information corresponding to the service, namespace information to which the service belongs in the cluster, and a cluster identifier; Generate the access domain name of the application service according to the service information, including: The service name, the namespace information of the service in the cluster, the cluster identifier, the generic domain name suffix and the node port information corresponding to the service are spliced according to the set domain name format to generate the access domain name of the application service, wherein the generic The domain name suffix is the suffix of the generic domain name associated with the domain name resolver. 4. The method according to claim 3, wherein registering the access domain name in the domain name resolver comprises: The mapping relationship between the access address and node port information of the cluster where the service is deployed and the access domain name is registered in the domain name resolver according to the cluster ID and the custom resource ID. 5. The method according to claim 1, wherein saving the access domain name in the customized resource comprises: Save the access domain name and the service information in the status field of the customized resource. 6. The method according to claim 1, further comprising: In response to listening to the deletion event of the custom resource, delete the custom resource, and search for a mapping relationship record related to the custom resource from the domain name resolver according to the cluster ID and the custom resource ID, and delete the mapping Relationship records. 7. A device for externally exposing application services in a multi-cluster environment, characterized in that it includes: A custom resource creation module, configured to create a custom resource under the namespace of the application in response to an application deployment operation, where the custom resource includes service information exposed by the application; An access domain name generating module, configured to generate an access domain name of the application service according to the service information in response to listening to the creation event of the custom resource, and register the access domain name in the domain name resolver; The access domain name issuing module is configured to store the access domain name in the customized resource, so as to expose the application service to the outside through the access domain name. 8. The device according to claim 7, wherein the service information includes service name, node port information corresponding to the service, namespace information of the service in the cluster, and cluster identifier; The access domain name generation module is also used for: The service name, the namespace information of the service in the cluster, the cluster identifier, the generic domain name suffix and the node port information corresponding to the service are spliced according to the set domain name format to generate the access domain name of the application service, wherein the generic The domain name suffix is the suffix of the generic domain name associated with the domain name resolver. 9. An electronic device, characterized in that it comprises: one or more processors; storage means for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are made to implement the method according to any one of claims 1-6. 10. A computer-readable medium, on which a computer program is stored, wherein, when the program is executed by a processor, the method according to any one of claims 1-6 is implemented.

Images