CN114461303A - A method and apparatus for accessing services within a cluster - Google Patents

Abstract

The present disclosure provides a method and a device for accessing cluster internal services, wherein a cluster comprises at least one service component, each service component corresponds to at least one container group, and each container group loads corresponding internal services; the cluster is connected with a load balancer; the method comprises the following steps: receiving service request information through an external load balancer, wherein the service request information is used for requesting access to internal services of the cluster; determining a service component corresponding to the service request information based on a first configuration file prestored in the load balancer, and sending the service request information to the service component; and determining a target container group corresponding to the service request information based on a second configuration file prestored in the service component, sending the service request information to the target container group, and accessing the internal service in the target container group. Automatic service exposure is realized, and internal services in the cluster can be conveniently and directly accessed.

Description

A method and apparatus for accessing services within a cluster

technical field

The present disclosure relates to the technical field of cloud platforms, and in particular, to a method and apparatus for accessing services within a cluster.

Background technique

Due to the characteristics of cloud-native clusters, the services deployed in the cluster use the Internet protocol addresses in the cluster. Therefore, only the services inside the cluster can access each other, and the network outside the cluster cannot directly establish communication with the container group inside the cluster. . In the prior art, cloud native exposes services externally or internally through one or more combinations of cluster addresses, node ports, load balancing, and portals. However, when exposing services, more means are usually needed to achieve the goal. For example, when using the portal method to expose external services, additional manual service application is required.

SUMMARY OF THE INVENTION

The present disclosure provides an adaptive external exposure method and system, which are used to solve the defect of manual service application in the prior art, realize automatic external exposure of services, and can conveniently and directly access the internal services inside the cluster.

In a first aspect, the present disclosure provides a method for accessing an internal service of a cluster, the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads a corresponding internal service; the cluster connection There is a load balancer;

The method includes:

Receive service request information through an external load balancer, where the service request information is used to request access to internal services of the cluster;

Determine the service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and send the service request information to the service component;

Based on the second configuration file pre-stored in the service component, the target container group corresponding to the service request information is determined, the service request information is sent to the target container group, and the internal services in the target container group are sent to the target container group. to access.

According to the method for accessing a service within a cluster provided by the present disclosure, the service component includes: a controller and a service unit;

The determining the service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and sending the service request information to the service component includes:

determining the controller corresponding to the service request information based on the first configuration file pre-stored in the load balancer;

Obtain the service unit based on the controller, wherein the controller corresponds to the service unit one-to-one;

The service request information is sent to the controller, and the service request information is sent to the service unit through the controller.

According to the method for accessing services within a cluster provided by the present disclosure, before the determining of the service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, the method includes:

Obtain information of the controller through information interaction between the controller and the load balancer;

Based on the information of the controller, configure a corresponding service unit on the controller through the load balancer;

The service unit of the controller is recorded as a first configuration file by the load balancer.

According to the method for accessing a service within a cluster provided by the present disclosure, before determining the target container group corresponding to the service request information based on the second configuration file pre-stored in the service component, the steps include:

Add the entry resource for accessing the internal service in the target container group;

The ingress resource is synchronously acquired by the service component, and the ingress resource is converted into a corresponding second configuration file.

According to the method for accessing a service within a cluster provided by the present disclosure, the determining a service component corresponding to the service request information and sending the service request information to the service component includes:

Based on the first entry address of the received service request information, first configuration information corresponding to the first entry address is determined in the first configuration file, wherein the first configuration information includes: the first entry address, the first transmission Path and service component identification;

Determine the service component corresponding to the service request information based on the first configuration information;

Based on the first transmission path, the service request information is sent to the service component corresponding to the service component identifier.

According to the method for accessing services within a cluster provided by the present disclosure, the determining a target container group corresponding to the service request information, and sending the service request information to the target container group includes:

Based on the second entry address of the received service request information, second configuration information corresponding to the second entry address is determined in the second configuration file, wherein the second configuration information includes: the second entry address, the port address, The second transmission path and the target container group identifier;

determining a target container group corresponding to the service request information based on the second configuration information;

receiving, by the service component, the service request information based on the port address;

Based on the second transmission path, the service request information in the service component is sent to the target container group corresponding to the target container group identifier.

According to the method for accessing a service within a cluster provided by the present disclosure, the method further includes:

The first configuration file is updated by the load balancer in the event of an increase/decrease of the controller.

In a second aspect, the present disclosure provides an apparatus for accessing an internal service of a cluster, the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads a corresponding internal service; the cluster connection There is a load balancer;

The device includes:

a receiving module, configured to receive service request information through an external load balancer, wherein the service request information is used to request access to internal services of the cluster;

a determining module, configured to determine a service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and send the service request information to the service component;

A sending module, configured to determine a target container group corresponding to the service request information based on the second configuration file pre-stored in the service component, send the service request information to the target container group, and send the target container to the target container group. Access to internal services within the group.

In a third aspect, the present disclosure provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the program to achieve any of the above Steps of methods to access services inside the cluster.

In a fourth aspect, the present disclosure provides a non-transitory computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the method for accessing a service within a cluster according to any one of the above.

In a fifth aspect, the present disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method for accessing a service within a cluster according to any one of the above.

The present disclosure provides a method and device for accessing services within a cluster, firstly setting a load balancer outside the cluster, receiving request information for accessing the internal services of the cluster through the load balancer, and based on the first configuration file pre-stored in the load balancer, Determine the service component corresponding to the service request information in the cluster, and send the service request information to the service component. The service component is generated inside the cluster and does not require additional manual application for the service component; and then based on the service component The second configuration file pre-stored in the server determines the target container group corresponding to the service request information, sends the service request information to the target container group, and accesses the internal services in the target container group. The automated services are exposed to the outside world, and the internal services within the cluster can be easily and directly accessed.

Description of drawings

In order to illustrate the present disclosure or the technical solutions in the prior art more clearly, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are the For the disclosed embodiments, for those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

FIG. 1 is a schematic flowchart of a method for accessing an internal service of a cluster according to an embodiment of the present disclosure;

2 is one of the schematic flowcharts of sending service request information to the service component provided by an embodiment of the present disclosure;

3 is a schematic flowchart of obtaining a first configuration file provided by an embodiment of the present disclosure;

FIG. 4 is the second schematic flowchart of sending service request information to the service component provided by an embodiment of the present disclosure;

5 is a schematic flowchart of sending service request information to a target container group provided by an embodiment of the present disclosure;

FIG. 6 is a block diagram of accessing an internal service of a cluster provided by an embodiment of the present disclosure;

7 is a schematic diagram of an overall flow of accessing an internal service of a cluster provided by an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of an apparatus for accessing services within a cluster provided by an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an electronic device provided by the present disclosure.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments It is a part of the embodiments of the present disclosure, but not all of the embodiments. Based on the embodiments in the embodiments of the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without creative work fall within the protection scope of the embodiments of the present disclosure.

Cloud native is a software development technology that leverages cloud computing to deploy applications as microservices using a software technology stack. In the prior art, cloud-native applications are built as a set of microservices running in Docker containers, orchestrated in Kubernetes, and managed and deployed using DevOps and GitOps workflows. Using a Docker container can package all the software and environment configuration required for execution into an executable package. Containers run in a virtualized environment, isolating the contained application from its environment.

Kubernetes, abbreviated as K8s, is a container cluster management system initiated and maintained by the Google team. The bottom layer is based on container technologies such as Docker and Rkt, providing powerful application management and resource management scheduling capabilities. K8s has complete cluster management capabilities, including multi-level security protection and access mechanisms, multi-tenant application support capabilities, transparent service registration and service discovery mechanisms, built-in intelligent load balancers, powerful fault discovery and self-healing functions, Service rolling upgrade and online expansion capabilities, scalable automatic resource scheduling mechanism, and multi-granularity resource allocation management capabilities. At the same time, K8s provides comprehensive management tools, which cover all aspects including development, test deployment, and operation and maintenance monitoring. Therefore, K8s is a brand-new distributed architecture solution based on container technology, and is a one-stop, complete distributed system development and support platform.

External service exposure refers to exposing the application services inside the cluster to the outside, so that the network outside the cluster can access the application services inside the cluster.

Internal service exposure is used for service access inside the cluster, that is, given a service in the cluster, other applications in the cluster can access the service, but cannot access it outside the cluster.

The network model of Kubernetes cluster is a widely used leading solution of container-based distributed architecture, which solves the management problems of large-scale clusters in use. In a Kubernetes cluster, a container group Pod is the smallest unit deployed in a Kubernetes cluster. It provides a certain service to the client, and usually assigns an Internet Protocol address within the cluster to the service.

However, due to the characteristics of the Kubernetes cluster, the services deployed in the Kubernetes cluster use the Internet Protocol addresses in the cluster. Therefore, only the services inside the Kubernetes cluster can access each other, and the network outside the cluster cannot directly communicate with the internal Kubernetes cluster. Pods establish communication. In the existing technology, Kubernetes can provide highly available microservices. In order to access these services, Kubernetes provides four methods: ClusterIP, Nodeport, Loadbalancer, and Ingress.

1) The ClusterIP service is the default service of Kubernetes. It is used for service access inside the cluster, that is, given a service in the cluster, other applications in the cluster can access the service, but cannot access it outside the cluster.

2) The NodePort service is the most primitive way to direct external traffic to services within a container group. This method mainly opens a specific port on all nodes (nodes can be virtual machines), and any traffic sent to this port is forwarded to the corresponding service. Nodeport is more convenient to use and is suitable for development and testing. However, the number of Nodeports is limited, and the number of Kubernetes services exposed by Nodeport is limited.

3) The LoadBalancer service is a standard way of exposing services to the Internet. On GKE, this method will start a Network Load Balancer, which will be given a single IP address, and all traffic to the specified IP address will be forwarded to the corresponding service. This way there are no filtering conditions, no routing, etc. That is, any kind of traffic can be sent to the service, like HTTP, TCP, UDP, Websocket, gRPC or any other kind. However, the biggest disadvantage of this method is that each service exposed with LoadBalancer will have its own IP address, and each LoadBalancer used will need to be paid, which will be very expensive.

4) Ingress is a k8s resource object, which is used to expose services to the outside world. However, when using Ingress to expose external services, you need to apply for additional services manually.

The embodiments of the present disclosure provide a method for accessing internal services of a cluster, which utilizes the built-in Ingress-controller and external load balancer of the cluster to realize automatic external exposure of services, and can conveniently and directly access the internal services inside the cluster.

Referring to FIG. 1, which is a schematic flowchart of a method for accessing services within a cluster according to an embodiment of the present disclosure, the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads The corresponding internal service; the cluster is connected with a load balancer.

A cluster is a collection of computing, storage and network resources. K8s uses these resources to run various container-based applications. The cluster can be used as a virtual machine. Each constituent point of the cluster is called a node (Node), and the nodes are combined to form a cluster. The responsibility of Node is to run container applications. Node is responsible for monitoring and reporting the status of the container, and managing the life cycle of the container according to the requirements of the Cluster. Node runs on the Linux operating system, and can also be a physical machine or a virtual machine.

A node (Node) includes multiple container groups. A container group refers to a Pod. A Pod is a basic management unit in K8s, not a container. A Pod is a layer of encapsulation of K8s on a container. Consists of one or more containers running on the same host.

The method includes:

110. Receive service request information through an external load balancer, where the service request information is used to request access to an internal service of the cluster.

In this step, the meaning of load balancer (Load Balance) means that the load (service request information) is balanced and distributed to different container groups in the cluster for execution, so as to complete the work tasks collaboratively. In the case where the services provided by different nodes in the same cluster are consistent, the load balancer will play the role of traffic distribution and distribute traffic to different nodes (container groups).

The service request information may include: the request method for the service, the identifier of the service, the protocol used, or the domain name of the internal service of the Kubernetes cluster, etc.

120. Determine a service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and send the service request information to the service component.

In this step, the first configuration file can be understood as key information of all service components in the cluster.

A service component can be understood as a logical collection composed of multiple container group objects defined by rules, and a policy for accessing this group of container groups.

130. Based on the second configuration file pre-stored in the service component, determine a target container group corresponding to the service request information, send the service request information to the target container group, and analyze the target container group for the service request information. access to internal services.

In this step, the second configuration file can be understood as key information of all container groups.

The present disclosure provides a method for accessing services within a cluster. First, a load balancer is set outside the cluster, request information for accessing the internal services of the cluster is received through the load balancer, and the cluster is determined based on a first configuration file pre-stored in the load balancer. The service component corresponding to the service request information is sent to the service component, and the service component is generated inside the cluster, and no additional manual application for the service component is required; based on the pre-stored service component the second configuration file, determine the target container group corresponding to the service request information, send the service request information to the target container group, and access the internal services in the target container group. The automated services are exposed to the outside world, and the internal services within the cluster can be easily and directly accessed.

Based on any of the foregoing embodiments, the service component includes: a controller and a service unit.

The controller refers to Ingress-controller. Ingress-controller is an Nginx container, which plays a forwarding role. The traffic in the real network is first imported to the Node where the Ingress-controller is installed, and then the Ingress-controller diverts the traffic to the back-end Pod according to the Ingress rules.

Ingress-controller can be implemented by any service program with reverse proxy function, such as Nginx, Envoy and Traefik, etc. Ingress-controller itself is also a Pod resource object running in the cluster, and it runs on the same network as the proxied application running as a Pod resource.

The service unit refers to a Service, specifically a Service of a NodePort type, and a NodePort is a type that guides external traffic into the cluster and accesses internal services.

The Pod service behind can be accessed through the Service. It should be noted that, in fact, the Service is not directly connected to the Pod object. There is also an intermediate layer between the Service and the Pod - the Endpoints resource object, which is a list composed of IP and ports. By default, when a Service resource object is created, its associated Endpoints object is automatically created.

Referring to FIG. 2, one of the schematic flowcharts of sending service request information to the service component provided by an embodiment of the present disclosure includes:

210. Determine a controller corresponding to the service request information based on the first configuration file pre-stored in the load balancer.

In this step, the key information of the service component is stored in the first configuration file. Therefore, the Ingress-controller corresponding to the service request information is determined based on the first configuration file pre-stored in the load balancer.

220. Acquire the service unit based on the controller, where the controller corresponds to the service unit one-to-one.

In this step, the Ingress-controller and the Service are generated in a one-to-one correspondence, and when the Ingress-controller is obtained, the Service is obtained accordingly.

230. Send the service request information to the controller, and send the service request information to the service unit through the controller.

In this step, the service request information is sent to the Ingress-controller, which is then sent to the corresponding Service by the Ingress-controller.

Referring to FIG. 3, a schematic flowchart of obtaining a first configuration file provided by an embodiment of the present disclosure includes:

310. Obtain information of the controller by performing information interaction between the controller and the load balancer.

In this step, all Ingress-controllers in the cluster will automatically interact with the external load balancer, and the external load balancer will record the key information of these Ingress-controllers.

320. Based on the information of the controller, configure a corresponding service unit for the controller through the load balancer.

In this step, the load balancer will apply for a NodePort-type Service for the Ingress-controller in the cluster according to the key information, that is, configure the corresponding service unit.

330. Use the load balancer to record the service unit of the controller as a first configuration file.

In this step, in the external load balancer, the configured Service is recorded as the first configuration file, which contains the IP address of the Node where the Ingress-controller is located, and the port in the Service, which can be configured in the external load balancer Load balancing algorithm.

Based on any of the foregoing embodiments, the following steps 130 to 132 are included before the step 130:

Step 131, adding an entry resource for accessing the internal service in the target container group.

In this step, the ingress resource refers to the Ingress resource. Ingress is one of the standard resource types of k8s. It is actually a set of rules that forward requests to specified Service resources based on DNS names or URL paths, which are used to forward request traffic from outside the cluster to the inside of the cluster to complete service publishing. However, the Ingress resource itself cannot perform traffic penetration. It is only a collection of rules. In order for these rules to work, they need the assistance of other functions, and the corresponding Ingress-controller needs to be configured.

Step 132: Synchronously acquire the entry resource through the service component, and convert the entry resource into a corresponding second configuration file.

In this step, the service component acquires the Ingress resource synchronously, and converts the Ingress resource into a second configuration file that can be loaded by itself.

Referring to FIG. 4 , the second schematic flowchart of sending service request information to the service component provided by an embodiment of the present disclosure includes:

410. Determine, in a first configuration file, first configuration information corresponding to the first entry address based on the first entry address receiving the service request information, where the first configuration information includes: the first entry address, the first entry address, the first entry address, and the first entry address. A transport path and service component identification.

In this step, the first entry address refers to the IP address specified in the Ingress resource, that is, the IP address of the load balancer. If there is no special designation in the Ingress resource, the access IP address is automatically allocated.

420. Determine a service component corresponding to the service request information based on the first configuration information.

In this step, the first configuration information includes related information of the service components in the cluster, therefore, the corresponding service components are determined according to the service request information.

430. Based on the first transmission path, send the service request information to a service component corresponding to the service component identifier.

In this step, the first transmission path path is the first transmission path specified in the Ingress resource, and based on the first transmission path, the service request information is sent to the service component corresponding to the service component identifier.

Referring to FIG. 5 , a schematic flowchart of sending service request information to a target container group provided by an embodiment of the present disclosure includes:

510. Determine second configuration information corresponding to the second entry address in the second configuration file based on the second entry address of the received service request information, where the second configuration information includes: the second entry address, the port address, second transmission path, and target container group identification.

In this step, the second entry address refers to the entry address for entering the cluster.

520. Determine a target container group corresponding to the service request information based on the second configuration information.

530. Receive, by the service component, the service request information based on the port address.

In this step, the port address is the same as the port address specified in the Ingress resource, that is, the port address of the service component entering the cluster.

540. Based on the second transmission path, send the service request information in the service component to a target container group corresponding to the target container group identifier.

In this step, Path is the second transmission path specified in the Ingress resource, and the backend is the Service specified in the Ingress resource.

Based on the second transmission path specified in the Ingress resource, the service request information in the service component is sent to the target container group corresponding to the target container group identifier.

Based on any of the above embodiments, the method further includes:

The first configuration file is updated by the load balancer in the event of an increase/decrease of the controller.

In this step, when the Ingress-controller expands or shrinks, that is, when the controller increases/decreases, the external load balancer will automatically update the first configuration file. The events that cause the Ingress-controller to expand or shrink include: service elimination events, service creation events, etc.

Further, to further explain the implementation of the present disclosure, referring to FIG. 6 , a block diagram of accessing services within a cluster provided by an embodiment of the present disclosure includes an external load balancer, and the cluster includes an Ingress-controller, a Service, and a Pod. . The number of service components in a cluster can be set according to specific scenarios. A cluster in Figure 6 includes two Ingress-controllers, corresponding to two Services respectively.

Referring to FIG. 7 , a schematic diagram of an overall flow of accessing services within a cluster provided by an embodiment of the present disclosure includes the following steps 710 to 750 :

Before performing steps 710 to 750, the first configuration file and the second configuration file need to be set in advance, specifically:

The process of setting up the first configuration file:

The Ingress-controller interacts with the load balancer to obtain the information of the Ingress-controller. According to the information of the Ingress-controller, the load balancer configures the NodePort type Service for the Ingress-controller.

The process of setting up the second configuration file:

Add Ingress resources to access internal services in the target container group, and make Ingress-controller and Service obtain Ingress resources synchronously.

710. The external load balancer receives service request information for accessing the internal service of the container group in the cluster.

720. The ingress address is the IP address of the load balancer, and based on the first transmission path specified in the Ingress resource, the service request information is transmitted to the load balancer, and the back end is the service component.

730. Determine an Ingress-controller corresponding to the service request information based on the first configuration file in the load balancer, and determine a Service of NodePort type according to the Ingress-controller.

740, the entry address is the address of entering the cluster, the port address is the address of entering the service component, the service request information is sent to the Ingress-controller, and the service request information is sent to the back-end Service through the Ingress-controller.

750. Based on the second transmission path specified in the Ingress resource, send the Service service request information to the target container group corresponding to the target container group identifier, and access the internal services in the target container group.

The following describes an apparatus for accessing a service within a cluster provided by an embodiment of the present disclosure. The apparatus for accessing a service within a cluster described below and the method for accessing a service within a cluster described above may refer to each other correspondingly.

Referring specifically to FIG. 8 , which is a schematic structural diagram of an apparatus for accessing services within a cluster according to an embodiment of the present disclosure, the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group Load the corresponding internal service; the cluster is connected with a load balancer.

The device includes:

810 A receiving module, configured to receive service request information through an external load balancer, where the service request information is used to request access to an internal service of the cluster.

820. A determining module, configured to determine a service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and send the service request information to the service component.

830 A sending module, configured to determine a target container group corresponding to the service request information based on the second configuration file pre-stored in the service component, send the service request information to the target container group, and send the target container group to the target container group. Internal services within the container group to access.

A device for accessing services within a cluster provided by the present disclosure firstly sets a load balancer outside the cluster, receives request information for accessing the internal services of the cluster through the load balancer, and determines the cluster based on a first configuration file pre-stored in the load balancer The service component corresponding to the service request information is sent to the service component, and the service component is generated inside the cluster, and no additional manual application for the service component is required; based on the pre-stored service component the second configuration file, determine the target container group corresponding to the service request information, send the service request information to the target container group, and access the internal services in the target container group. The automated services are exposed to the outside world, and the internal services within the cluster can be easily and directly accessed.

Based on any of the foregoing embodiments, the service component includes: a controller and a service unit.

The 820 determination module is specifically used for:

The controller corresponding to the service request information is determined based on the first configuration file pre-stored in the load balancer.

The service unit is acquired based on the controller, wherein the controller and the service unit are in one-to-one correspondence.

The service request information is sent to the controller, and the service request information is sent to the service unit through the controller.

Based on any of the foregoing embodiments, before the 820 determination module, the method includes:

an obtaining module, configured to exchange information with the load balancer through the controller to obtain the information of the controller.

A configuration module, configured to configure a corresponding service unit for the controller through the load balancer based on the information of the controller.

A recording module, configured to record the service unit of the controller as a first configuration file through the load balancer.

Based on any of the above embodiments, before 830 the sending module, include:

The adding module is used to add the entry resource for accessing the internal service in the target container group.

A conversion module, configured to obtain the entry resource synchronously through the service component, and convert the entry resource into a corresponding second configuration file.

Based on any of the foregoing embodiments, the 820 determination module is further configured to:

Based on the first entry address of the received service request information, first configuration information corresponding to the first entry address is determined in the first configuration file, wherein the first configuration information includes: the first entry address, the first transmission Path and service component ID.

A service component corresponding to the service request information is determined based on the first configuration information.

Based on the first transmission path, the service request information is sent to the service component corresponding to the service component identifier.

Based on any of the foregoing embodiments, the 830 sending module is configured to:

Based on the second entry address of the received service request information, second configuration information corresponding to the second entry address is determined in the second configuration file, wherein the second configuration information includes: the second entry address, the port address, The second transmission path and target container group identifier.

A target container group corresponding to the service request information is determined based on the second configuration information.

The service request information is received by the service component based on the port address.

Based on the second transmission path, the service request information in the service component is sent to the target container group corresponding to the target container group identifier.

Based on any of the foregoing embodiments, the apparatus further includes:

An update module, configured to update the first configuration file through the load balancer when the controller increases/decreases.

FIG. 9 illustrates a schematic diagram of the physical structure of an electronic device. As shown in FIG. 9 , the electronic device may include: a processor (processor) 910, a communication interface (Communications Interface) 920, a memory (memory) 930, and a communication bus 940, The processor 910 , the communication interface 920 , and the memory 930 communicate with each other through the communication bus 940 . The processor 910 may invoke the logic instructions in the memory 930 to execute a method for accessing services within a cluster, where the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads corresponding internal services; the cluster is connected with a load balancer; the method includes: receiving service request information through an external load balancer, wherein the service request information is used to request access to internal services of the cluster; based on the load The first configuration file pre-stored in the balancer determines the service component corresponding to the service request information, and sends the service request information to the service component; based on the second configuration file pre-stored in the service component, determines the service component. the target container group corresponding to the service request information, send the service request information to the target container group, and access the internal services in the target container group.

In addition, the above-mentioned logic instructions in the memory 930 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present disclosure are essentially or contribute to the prior art or parts of the technical solutions may be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

In another aspect, the present disclosure also provides a computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer When executing, the computer can execute a method for accessing the internal services of the cluster provided by the above methods, the cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads the corresponding internal service. ; the cluster is connected with a load balancer; the method includes: receiving service request information through an external load balancer, wherein the service request information is used to request access to internal services of the cluster; based on the load balancer The first configuration file pre-stored in the service component is determined, and the service component corresponding to the service request information is determined, and the service request information is sent to the service component; based on the second configuration file pre-stored in the service component, the service component is determined. The target container group corresponding to the request information sends the service request information to the target container group, and accesses the internal services in the target container group.

In yet another aspect, the present disclosure also provides a non-transitory computer-readable storage medium on which a computer program is stored, and the computer program is implemented when executed by a processor to execute a method for accessing a service within a cluster provided by each of the above, The cluster includes at least one service component, each service component corresponds to at least one container group, and each container group loads corresponding internal services; the cluster is connected with a load balancer; the method includes: using an external load balancer Receive service request information, where the service request information is used to request access to internal services of the cluster; determine the service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, and assign The service request information is sent to the service component; based on the second configuration file pre-stored in the service component, a target container group corresponding to the service request information is determined, and the service request information is sent to the target container group , and access the internal services in the target container group.

The device embodiments described above are only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed over multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

From the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and certainly can also be implemented by hardware. Based on this understanding, the above-mentioned technical solutions can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic A disc, an optical disc, etc., includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in various embodiments or some parts of the embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure, but not to limit them; although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims (11)

1. A method for accessing cluster internal services, wherein the cluster comprises at least one service component, each service component corresponds to at least one container group, and each container group loads corresponding internal services; the cluster is connected with a load balancer;

the method comprises the following steps:

receiving service request information through an external load balancer, wherein the service request information is used for requesting access to internal services of the cluster;

determining a service component corresponding to the service request information based on a first configuration file prestored in the load balancer, and sending the service request information to the service component;

and determining a target container group corresponding to the service request information based on a second configuration file prestored in the service component, sending the service request information to the target container group, and accessing the internal service in the target container group.

2. The method of accessing intra-cluster services of claim 1, wherein the service component comprises: a controller and a service unit;

the determining a service component corresponding to the service request information based on a first configuration file prestored in the load balancer, and sending the service request information to the service component includes:

determining a controller corresponding to the service request information based on a first configuration file prestored in the load balancer;

acquiring the service units based on the controller, wherein the controller corresponds to the service units one by one;

and sending the service request information to the controller, and sending the service request information to the service unit through the controller.

3. The method according to claim 2, wherein before determining the service component corresponding to the service request information based on the first configuration file pre-stored in the load balancer, the method comprises:

performing information interaction with the load balancer through the controller to acquire information of the controller;

configuring a corresponding service unit for the controller through the load balancer based on the information of the controller;

recording, by the load balancer, a service unit of the controller as a first configuration file.

4. The method according to claim 1, wherein before determining the target container group corresponding to the service request information based on the second configuration file pre-stored in the service component, the method comprises:

adding an entry resource that accesses an internal service within the target container group;

and synchronously acquiring the entry resources through the service assembly, and converting the entry resources into corresponding second configuration files.

5. The method according to claim 1, wherein the determining a service component corresponding to the service request information and sending the service request information to the service component comprises:

determining first configuration information corresponding to a first entry address in a first configuration file based on the first entry address for receiving service request information, wherein the first configuration information comprises: a first entry address, a first transmission path and a service component identification;

determining a service component corresponding to the service request information based on the first configuration information;

and sending the service request information to a service component corresponding to the service component identification based on the first transmission path.

6. The method according to claim 1, wherein the determining a target group of containers to which the service request information corresponds, and the sending the service request information to the target group of containers comprises:

determining second configuration information corresponding to a second entry address in a second configuration file based on the second entry address for receiving the service request information, wherein the second configuration information comprises: a second ingress address, a port address, a second transmission path, and a target container group identification;

determining a target container group corresponding to the service request information based on the second configuration information;

receiving, by the service component, the service request information based on the port address;

and sending the service request information in the service assembly to a target container group corresponding to the target container group identification based on a second transmission path.

7. The method of accessing intra-cluster services of claim 2, further comprising:

updating, by the load balancer, the first profile in the event the controller is increased/decreased.

8. An apparatus for accessing internal services of a cluster, wherein the cluster comprises at least one service component, each service component corresponds to at least one container group, and each container group loads the corresponding internal service; the cluster is connected with a load balancer;

the device comprises:

the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving service request information through an external load balancer, and the service request information is used for requesting to access internal services of the cluster;

the determining module is used for determining a service component corresponding to the service request information based on a first configuration file prestored in the load balancer and sending the service request information to the service component;

and the sending module is used for determining a target container group corresponding to the service request information based on a second configuration file prestored in the service component, sending the service request information to the target container group and accessing the internal service in the target container group.

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of accessing intra-cluster services according to any of claims 1 to 7 when executing the program.

10. A non-transitory computer readable storage medium, having stored thereon a computer program, characterized in that the computer program, when being executed by a processor, is adapted to carry out the steps of the method of accessing intra-cluster services according to any of the claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method for accessing a cluster internal service according to any one of claims 1 to 7 when executed by a processor.

Images