Method and system for exposing resources in kubernetes, equipment and medium

Abstract

The invention discloses a method for exposing resources in kubernetes. The method comprises the following steps of: in response to a received request for applying for service resources, judging whether a mapping relationship between a label corresponding to a type of the service resources and a virtual IP exists in a first configuration file of keepalived service or not; in response to the absenceof the mapping relationship, acquiring a new virtual IP and establishing a mapping relationship between the new virtual IP and the label in the first configuration file; and binding the virtual IP corresponding to the label in the first configuration file to a plurality of pods corresponding to the service resources, so as to expose the plurality of pods to the outside of a kubernetes cluster byusing the virtual IP. The invention further discloses a system, computer equipment and a readable storage medium. According to the method provided by the invention, the virtual IP (VIP) is enabled tocorrespond to each pod of the service resources through keepalived, and the VIP is exposed out of the kubernetes cluster, so that each pod of the service resources is exposed out of the kubernetes cluster, and meanwhile, the problem of service interruption caused by DNS is avoided.

Description

technical field [0001] The present invention relates to the field of kubernetes, in particular to a resource exposure method, system, device and storage medium in kubernetes. Background technique [0002] In kubernetes, a variety of ways to expose services to the outside world are provided, such as nodeport, L7ingress, and L4 LoadBalancer. However, because these methods are based on DNS, they do not provide true High Availability (HA) of multiple copies of pods. The main cause of the problem is that in a multi-replica pod, when a replica goes down, DNS does not perceive that there is an abnormal pod, and some traffic will still be imported to the abnormal pod until DNS finds that the pod is abnormal. Only by correcting the traffic direction, the import of abnormal traffic to the abnormal pod will be stopped. Contents of the invention [0003] In view of this, in order to overcome at least one aspect of the above problems, an embodiment of the present invention proposes a ...

AI Technical Summary

Problems solved by technology

[0002] In kubernetes, there are many ways to expose services to the outside world, such as nodeport, L7ingress, and L4 LoadBalancer. However, because these methods are based on DNS, they do not provide real High Availability (HA) of multiple copies of pods.

The main cause of the problem is that in a multi-replica pod, when a replica goes down, DNS does not perceive that there is an abnormal pod, and some traffic will still be imported to the abnormal pod until DNS finds that the pod is abnormal. And correct the traffic direction, it will stop importing abnormal traffic into the abnormal pod

Images