WO2023197874A1 - 一种应用访问方法、装置、设备及介质 - Google Patents

一种应用访问方法、装置、设备及介质 Download PDF

Info

Publication number
WO2023197874A1
WO2023197874A1 PCT/CN2023/084815 CN2023084815W WO2023197874A1 WO 2023197874 A1 WO2023197874 A1 WO 2023197874A1 CN 2023084815 W CN2023084815 W CN 2023084815W WO 2023197874 A1 WO2023197874 A1 WO 2023197874A1
Authority
WO
WIPO (PCT)
Prior art keywords
pod
information
endpoint
request
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/084815
Other languages
English (en)
French (fr)
Inventor
黄吉旺
吴栋
王玉东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Wave Intelligent Technology Co Ltd
Original Assignee
Suzhou Wave Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Wave Intelligent Technology Co Ltd filed Critical Suzhou Wave Intelligent Technology Co Ltd
Publication of WO2023197874A1 publication Critical patent/WO2023197874A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare

Definitions

  • This application relates to the technical field of application access, and in particular to an application access method, device, equipment and medium.
  • master-slave mechanism is represented by one of the replicas acting as the master replica to respond to requests for the application, and the remaining replicas running as slave replicas.
  • master replica When the master replica is abnormal, one of the slave replicas becomes the master replica to take over the traffic.
  • This mechanism can ensure atomicity and avoid data processing inconsistencies that may be caused by multiple copies responding to requests at the same time.
  • the technical implementation plan of master-slave is generally to develop or integrate an election mechanism in the source code. By continuously running the election process, the master copy role of a certain copy is maintained. The master copy responds to the request.
  • the purpose of this application is to provide an application access method, device, equipment and medium that can reduce the complexity of application development and improve the response performance of application access.
  • the specific plan is as follows:
  • Some embodiments of the present application disclose an application access method, applied to a preset admission controller, including:
  • the platform creates or updates endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • the pod information corresponding to each pod ip in the pod ip list it also includes:
  • the service information is the information of the service corresponding to the endpoint;
  • the step of querying the pod information corresponding to each pod ip in the pod ip list is triggered.
  • a main pod is determined from all pods of the target application based on all pod information and preset policies, including:
  • the pod with the earliest creation time is determined from all pods of the target application as the main pod.
  • a main pod is determined from all pods of the target application based on all pod information and preset policies, including:
  • the pod with the latest creation time is determined from all pods of the target application as the main pod.
  • the k8s platform before parsing the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, it also includes:
  • Some embodiments of the present application also disclose an application access device, applied to a preset admission controller, including:
  • the request parsing module is used to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information;
  • the list acquisition module is used to obtain the pod ip list corresponding to the target application from the request parsing information
  • Information query module used to query the pod information corresponding to each pod ip in the pod ip list
  • the main pod determination module is used to determine a main pod from all pods of the target application based on all pod information and preset policies;
  • the information update module is used to replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create or update endpoints based on the replacement request information to forward all access traffic of the target application. to the main pod.
  • the endpoint name acquisition module is used to obtain the endpoint name from the request parsing information
  • the service information query module is used to query service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint;
  • the master-slave label judgment module is used to determine whether there is a preset master-slave label in the service information; if there is a preset master-slave label and the value of the preset master-slave label is the first preset value, the information query module is triggered to execute the query pod Steps for pod information corresponding to each pod ip in the ip list.
  • Some embodiments of the present application also disclose an electronic device, including a processor and a memory; wherein,
  • Memory used to hold computer programs
  • the processor is used to execute the computer program to implement the aforementioned application access method.
  • Some embodiments of the present application also disclose a computer non-volatile readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the aforementioned application access method is implemented.
  • this application first parses the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtains the pod ip list corresponding to the target application from the request parsing information, and queries each pod ip in the pod ip list. Corresponding pod information, then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information. This allows the k8s platform to create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • this application uses the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtains the request parsing information, and determines a main pod based on the request parsing information and the preset policy. Use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all the access traffic of the target application to the main pod, avoiding complex and difficult-to-maintain problems.
  • the election mechanism and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • Figure 1 is a flow chart of an application access method disclosed in some embodiments of the present application.
  • Figure 2 is a schematic diagram of a specific application access solution provided by some embodiments of the present application.
  • Figure 3 is a schematic structural diagram of an application access device disclosed in some embodiments of the present application.
  • Figure 4 is a structural diagram of an electronic device disclosed in some embodiments of the present application.
  • Figure 5 is a schematic structural diagram of a computer non-volatile readable storage medium provided by some embodiments of the present application.
  • kubernetes a common open source container orchestration architecture for container cloud platforms, which can realize automatic scheduling, expansion, fault recovery, etc. of containers, referred to as k8s.
  • kube-apiserver k8s’ external service API (Application Programming Interface, application programming interface). All resource-related operations in k8s need to be implemented by calling the kube-apiserver related interface.
  • Workload The deployment form of application components on k8s, including deployment (stateless load)/statefulset (stateful load)/job (task)/cronjob (timed task)/daemonset (daemon process) and other forms. Each workload can manage 1 or more pods.
  • Pod The smallest management unit of k8s, consisting of one or more containers. These containers share namespaces such as processes and networks.
  • Service An object resource designed by k8s to satisfy requests for workloads. It matches pods under the workload through labelselector and provides load balancing capabilities to forward traffic to different pods.
  • endpoint a set of pod IPs and ports. When the service is created, the pod corresponding to the workload is selected based on the labelselector of the service. Access to the service will be loaded to a certain pod IP and port on the endpoint through load balancing.
  • the master-slave technical implementation plan is generally to develop or integrate an election mechanism in the source code.
  • the master copy role of a certain copy is maintained.
  • the master copy responds to the request.
  • a new primary copy is re-elected from the backup copy.
  • the secondary copy needs to forward the traffic to the primary copy to avoid No need to manipulate data from copies.
  • This solution not only has complex technical principles and is difficult to maintain, but also has response performance problems caused by the slave replica forwarding traffic to the master replica again.
  • this application discloses an application access solution that can reduce the complexity of application development and improve the response performance of application access.
  • an application access method which is applied to a preset admission controller, including:
  • Step S11 Parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information.
  • the request information includes the pod IPs of all pods of the target application found by the k8s platform, and the endpoint name of the endpoint to be created or updated.
  • some embodiments of this application obtain the endpoint initiated by the k8s platform based on the admission webhook mechanism (a type of admission control plug-in that can be used to intercept all requests sent to APISERVER, and can modify the request or reject the request) Create request or endpoint update request.
  • the admission webhook mechanism a type of admission control plug-in that can be used to intercept all requests sent to APISERVER, and can modify the request or reject the request
  • Containerized applications are deployed on k8s clusters in the form of workloads, and each workload can run one or more instances (pods) at the same time.
  • K8s provides a service mechanism to access workloads. Each service has a corresponding access address outside the cluster or within the cluster, and provides a load balancing function to achieve load access to multiple pods. After each service is created, k8s will create an endpoint resource with the same name in real time. This resource contains all pod IPs and ports to be loaded by the service. Access to the service will be loaded to a certain pod IP and port on the endpoint through load balancing. superior.
  • k8s provides an admission webhook mechanism, which allows calling a custom admission controller to perform verification and modification actions during the resource creation process.
  • some embodiments of this application are based on k8s's service and endpoint resource management and combine with webhook Mechanism, develop a master-slave high-availability admission controller, obtain a preset admission controller, and deploy the preset admission controller on the container platform in advance and register it in the k8s platform.
  • k8s creates an endpoint, it calls the default admission controller and passes the endpoint creation request to the default admission controller.
  • Step S12 Obtain the pod IP list corresponding to the target application from the request resolution information.
  • some embodiments of this application can also obtain the endpoint name from the request parsing information; query the service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint; determine whether there is a preset master-slave tag in the service information; If there is a preset master-slave label and the value of the preset master-slave label is the first preset value, the step of querying the pod information corresponding to each pod ip in the pod ip list is triggered. If there is no default master-slave tag, or there is a default master-slave tag and the value of the default master-slave tag is the second default value, no processing is performed.
  • the endpoint name is the service name, so you can query based on the endpoint name. service information.
  • application developers create services for their applications, they can add a label to the service, that is, a default master-slave label, based on whether there is a requirement for master-slave high availability.
  • Step S13 Query the pod information corresponding to each pod ip in the pod ip list.
  • pod information can include creation time, name, etc.
  • Step S14 Determine a main pod from all pods of the target application based on all pod information and preset policies.
  • the pod with the earliest creation time can be determined from all pods of the target application based on all pod information and preset policies as the main pod. It is understandable that the earliest pods created are more stable.
  • the pod with the latest creation time can be determined from all pods of the target application as the main pod based on all pod information and preset policies. It is understandable that the latest pod created is the pod created based on the latest application to facilitate the provision of updated application services.
  • all pods can be sorted according to their creation time, and the main pod is determined based on the sorting results.
  • the main pod can also be determined through other strategies.
  • Step S15 Replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create or update endpoints based on the replacement request information to forward all access traffic of the target application to the main pod. superior.
  • the request information can be a global variable, so that the preset admission controller can directly modify the request information.
  • the k8s platform when it detects that the pod of the target application has changed, it initiates an endpoint update request; when any pod in the target application becomes abnormal, is deleted, or a new pod is added, it is determined that the pod of the target application has changed. That is to say, some embodiments of this application call the preset admission controller during the process of creating an endpoint for a service, query the associated pod information based on all pod IPs in the current endpoint creation request, and select all pods from all pods according to the preset policy.
  • Filter a master pod in the pod, and use the pod ip of the pod to replace the pod ip list in the request information, so that the request traffic through the service is only forwarded to the pod, and the pod will respond to the request as the master copy.
  • k8s will automatically trigger an endpoint update request in real time. It will also call the preset admission controller through the admission webhook mechanism and select the new pod as the main pod again based on the same logic when creating the endpoint.
  • a service creates or updates an endpoint
  • a certain pod IP is selected as the pod IP in the endpoint according to the preset policy, that is, a pod is selected as the backend of the service load, thereby forwarding traffic directly to the pod.
  • the master-slave high-availability access mechanism of multi-copy applications is realized.
  • the application can focus on the business logic of the application itself, avoiding performance problems caused by forwarding traffic to the slave replicas, and developing and deploying it once. It can be used by all applications in the cluster that require it.
  • the overall solution is simple, flexible, and easy to expand. There is a new pod selection strategy that can directly modify the controller processing logic, and it has good reusability and scalability.
  • FIG. 2 is a schematic diagram of a specific application access solution disclosed in some embodiments of the present application.
  • the client initiates a request to create a service, adds a master-slave processing label to the service, and sets the labelselector of the service to the label of the application.
  • k8s receives the request, creates a service, and queries all pods corresponding to the application based on labelselector, obtains the pod ip list, determines the request information, initiates an endpoint creation request based on the request information, and calls the registered admission controller (preset accurate Admission controller), when a pod exception, deletion, or addition is detected, an endpoint update request is automatically initiated based on the current request information.
  • the registered admission controller preset accurate Admission controller
  • the business processing logic of the preset admission controller is: parse the endpoint creation or update request, and obtain the request Parse the information; obtain the endpoint name, pod ip list, etc. from the request parsing information; query the service information based on the endpoint name; determine whether the service has a master-slave label. If the label exists and the value is true, it means that the service requires master-slave access, then Carry out subsequent processing logic. If the tag does not exist, it means that the service does not require master-slave access, and the execution will not continue and will be completed directly.
  • Subsequent processing logic includes: querying all pod information based on the pod ip list, sorting by creation time from early to late, and obtaining the first pod ip; replacing the ip list in the original request information with the filtered pod ip so that k8 can update based on Create or update the endpoint with the request information.
  • some embodiments of this application first parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtain the pod ip list corresponding to the target application from the request parsing information, and query each pod ip list in the pod ip list.
  • pod information corresponding to each pod ip then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement Request information so that the k8s platform can create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • some embodiments of this application use the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtain the request parsing information, and determine an endpoint based on the request parsing information and the preset policy.
  • the main pod use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all access traffic of the target application to the main pod, avoiding complexity and The election mechanism that is not easy to maintain and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • an application access device which is applied to a preset admission controller, including:
  • the request parsing module 11 is used to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information;
  • the list acquisition module 12 is used to obtain the pod ip list corresponding to the target application from the request parsing information
  • Information query module 13 used to query the pod information corresponding to each pod ip in the pod ip list;
  • the main pod determination module 14 is used to determine a main pod from all pods of the target application based on all pod information and preset policies;
  • Information update module 15 used to replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create endpoints or updates based on the replacement request information to evenly distribute the access traffic of the target application. Forwarded to the main pod.
  • some embodiments of this application first parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtain the pod ip list corresponding to the target application from the request parsing information, and query each pod ip list in the pod ip list.
  • pod information corresponding to each pod ip then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement Request information so that the k8s platform can create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • some embodiments of this application use the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtain the request parsing information, and determine an endpoint based on the request parsing information and the preset policy.
  • Main pod use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all access traffic of the target application to the main pod, avoiding complexity and
  • the election mechanism that is not easy to maintain and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • the application access device further includes: an endpoint name acquisition module, configured to obtain the endpoint name from the request parsing information.
  • application access devices also include:
  • the service information query module is used to query service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint;
  • the master-slave tag judgment module is used to judge whether there is a preset master-slave tag in the service information; if there is a preset master-slave tag and the value of the preset master-slave tag is the first preset value, the information query module 13 is triggered to execute the query.
  • Each pod ip list Steps for pod information corresponding to pod ip. If there is no default master-slave tag, or there is a default master-slave tag and the value of the default master-slave tag is the second default value, no processing is performed.
  • the main pod determination module 14 is specifically configured to determine the pod with the earliest creation time from all pods of the target application based on all pod information and preset policies as the main pod.
  • the main pod determination module 14 is specifically configured to determine the pod with the latest creation time from all pods of the target application based on all pod information and preset policies as the main pod.
  • the application access device also includes a request acquisition module, which is used to obtain the endpoint creation request or endpoint update request initiated by the k8s platform based on the admission webhook mechanism.
  • some embodiments of the present application disclose an electronic device 20, which includes a processor 21 and a memory 22; the memory 22 is used to save the computer program; the processor 21 is used to execute the computer program.
  • the aforementioned implementation Example public application access methods.
  • the memory 22, as a carrier for resource storage may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the storage method may be short-term storage or permanent storage.
  • the electronic device 20 also includes a power supply 23, a communication interface 24, an input and output interface 25 and a communication bus 26; the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can provide the electronic device 20 with working voltage.
  • a data transmission channel with external devices and the communication protocol it follows is any communication protocol that can be applied to the technical solution of this application, which is not specifically limited here; the input and output interface 25 is used to obtain external input data or To output data to the outside world, the specific interface type can be selected according to specific application needs, and is not specifically limited here.
  • some embodiments of the present application also disclose a computer non-volatile readable storage medium for storing computer programs.
  • the computer non-volatile readable storage medium 5 stores computer programs. 51, wherein the computer program 51 implements the application access method disclosed in the foregoing embodiments when executed by the processor.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically programmable ROM
  • EEPly erasable programmable ROM registers, hard disks, removable disks, CD-ROM, or any other form of storage media known in the technical field.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种应用访问方法、装置、设备及介质，应用于应用访问技术领域，包括：解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；从请求解析信息中获取目标应用对应pod ip列表；查询pod ip列表中每个pod ip对应的pod信息；基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod；将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。能够降低应用开发的复杂度，并且提升应用访问的响应性能。

Description

一种应用访问方法、装置、设备及介质
相关申请的交叉引用
本申请要求于2022年04月11日提交中国专利局，申请号为202210371384.2，申请名称为“一种应用访问方法、装置、设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及应用访问技术领域，特别涉及一种应用访问方法、装置、设备及介质。
背景技术
在生产环境中，应用的高可用通常通过多副本来实现，在容器平台上，表现为多个pod，并有多主、主从等不同的请求处理机制。其中，主从的机制表现为其中一个副本作为主副本角色响应对该应用的请求，其余副本作为从副本角色运行，在主副本异常时由其中一个从副本变为主副本来接管流量。这种机制能够保证原子性，避免多个副本同时响应请求可能带来的数据处理不一致问题。主从的技术实现方案一般为在源码中开发或集成一套选举机制，通过持续运行该选举进程不停的维持某副本的主副本角色，由该主副本响应请求，当主副本失联时再从备份副本中重新选举出新的主副本，当流量到达从副本时，从副本需要把流量转发给主副本，避免从副本操作数据。这种方案不但技术原理复杂，不易维护，并且存在从副本要再次转发流量给主副本带来的响应性能问题。
发明内容
有鉴于此，本申请的目的在于提供一种应用访问方法、装置、设备及介质，能够降低应用开发的复杂度，并且提升应用访问的响应性能。其具体方案如下：
本申请的一些实施例公开了一种应用访问方法，应用于预设准入控制器，包括：
解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；
从请求解析信息中获取目标应用对应pod ip列表；
查询pod ip列表中每个pod ip对应的pod信息；
基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod；
将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s 平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。
在本申请的一些实施例中，还包括：
从请求解析信息中获取endpoint名称；
相应的，在查询pod ip列表中每个pod ip对应的pod信息之前，还包括：
基于endpoint名称查询service信息；其中，service信息为endpoint对应的service的信息；
判断service信息中是否存在预设主从标签；
若存在预设主从标签且预设主从标签的值为第一预设值，则触发查询pod ip列表中每个pod ip对应的pod信息的步骤。
在本申请的一些实施例中，还包括：
若不存在预设主从标签，或存在预设主从标签且预设主从标签的值为第二预设值，则不进行任何处理。
在本申请的一些实施例中，基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod，包括：
基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最早的一个pod，作为主pod。
在本申请的一些实施例中，基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod，包括：
基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最晚的一个pod，作为主pod。
在本申请的一些实施例中，解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求之前，还包括：
基于admission webhook机制获取k8s平台发起的endpoint创建请求或endpoint更新请求。
本申请的一些实施例还公开了一种应用访问装置，应用于预设准入控制器，包括：
请求解析模块，用于解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；
列表获取模块，用于从请求解析信息中获取目标应用对应pod ip列表；
信息查询模块，用于查询pod ip列表中每个pod ip对应的pod信息；
主pod确定模块，用于基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod；
信息更新模块，用于将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。
在本申请的一些实施例中，还包括：
endpoint名称获取模块，用于从请求解析信息中获取endpoint名称；
service信息查询模块，用于基于endpoint名称查询service信息；其中，service信息为endpoint对应的service的信息；
主从标签判断模块，用于判断service信息中是否存在预设主从标签；若存在预设主从标签且预设主从标签的值为第一预设值，则触发信息查询模块执行查询pod ip列表中每个pod ip对应的pod信息的步骤。
本申请的一些实施例还公开了一种电子设备，包括处理器和存储器；其中，
存储器，用于保存计算机程序；
处理器，用于执行计算机程序以实现前述的应用访问方法。
本申请的一些实施例还公开了一种计算机非易失性可读存储介质，用于保存计算机程序，其中，计算机程序被处理器执行时实现前述的应用访问方法。
可见，本申请先解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息，之后从请求解析信息中获取目标应用对应pod ip列表，并查询pod ip列表中每个pod ip对应的pod信息，然后基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod，最后将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。也即，本申请通过预设准入控制器对k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求进行解析，得到请求解析信息，并基于请求解析信息和预设策略确定出一个主pod，利用该主pod的pod ip替换掉请求信息中的pod ip列表，k8s平台基于该请求信息创建或更新的endpoint，能够将目标应用的访问流量均转发至主pod上，避免了复杂且不易维护的选举机制，以及从副本的转发流量带来的性能问题，能够降低应用开发的复杂度，并且提升应用访问的响应性能。
附图说明
为了更清楚地说明本申请一些实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据提供的附图获得其他的附图。
图1为本申请一些实施例公开的一种应用访问方法流程图；
图2为本申请一些实施例提供的一种具体的应用访问方案示意图；
图3为本申请一些实施例公开的一种应用访问装置结构示意图；
图4为本申请一些实施例公开的一种电子设备结构图；
图5为本申请一些实施例所提供的一种计算机非易失性可读存储介质的结构示意图。
具体实施方式
下面将结合本申请一些实施例中的附图，对本申请一些实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先，对本申请方案涉及到的关键术语进行解释：kubernetes：容器云平台通用的开源容器编排架构，能够实现容器的自动调度、扩展、故障恢复等，简称k8s。kube-apiserver：k8s的对外服务API(Application Programming Interface,应用程序编程接口)，k8s中所有资源的相关操作需要调用kube-apiserver相关接口来实现。工作负载：k8s上应用组件的部署形式，包括deployment(无状态负载)/statefulset(有状态负载)/job(任务)/cronjob(定时任务)/daemonset(守护进程)等多种形式。每个工作负载可以管理1个或多个pod。pod：k8s的最小管理单元，由1个或多个容器组成，这些容器共享进程、网络等命名空间。service：k8s为满足对工作负载的请求而设计的一个对象资源，通过labelselector匹配工作负载下的pod，并提供负载均衡能力将流量转发到不同pod。endpoint：一组pod ip和端口的集合，当service创建后，根据service的labelselector选择对应工作负载的pod。对service的访问将通过负载均衡后负载到endpoint上的某一个pod ip和端口上。
目前，主从的技术实现方案一般为在源码中开发或集成一套选举机制，通过持续运行该选举进程不停的维持某副本的主副本角色，由该主副本响应请求，当主副本失联时再从备份副本中重新选举出新的主副本，当流量到达从副本时，从副本需要把流量转发给主副本，避 免从副本操作数据。这种方案不但技术原理复杂，不易维护，并且存在从副本要再次转发流量给主副本带来的响应性能问题。为此，本申请公开了一种应用访问方案，能够降低应用开发的复杂度，并且提升应用访问的响应性能。
参见图1所示，本申请一些实施例公开了一种应用访问方法，应用于预设准入控制器，包括：
步骤S11：解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息。
其中，请求信息包括k8s平台查找到的目标应用的所有pod的pod ip，以及待创建或待更新endpoint的endpoint名称。在具体的实施方式中，本申请一些实施例基于admission webhook机制(准入控制插件的一种，可以用于拦截所有向APISERVER发送的请求，并且可以修改请求或拒绝请求)获取k8s平台发起的endpoint创建请求或endpoint更新请求。
需要指出的是，当前大部分容器云平台均基于k8s框架，面向用户提供以应用管理为核心的功能体系。容器化应用以工作负载的形式部署在k8s集群上，每个工作负载可以同时运行1个或多个实例(pod)。K8s提供service机制实现对工作负载的访问，每个service有对应的集群外或内部的访问地址，并且提供负载均衡功能来实现对多个pod的负载访问。每创建一个service后，k8s会实时创建一个同名的endpoint资源，该资源包含service要负载到的所有pod ip和端口，对service的访问将通过负载均衡后负载到endpoint上的某一个pod ip和端口上。进一步的，k8s提供admission webhook机制，允许在创建资源的过程中，调用自定义的admission controller，进行校验、修改动作，基于此，本申请一些实施例基于k8s的service、endpoint资源管理并结合webhook机制，开发主从高可用的准入控制器，得到预设准入控制器，并且，预先将预设准入控制器部署在容器平台上，并注册到k8s平台中。k8s在创建endpoint时，调用预设准入控制器，将endpoint创建请求传入预设准入控制器。
步骤S12：从请求解析信息中获取目标应用对应pod ip列表。
进一步的，本申请一些实施例还可以从请求解析信息中获取endpoint名称；基于endpoint名称查询service信息；其中，service信息为endpoint对应的service的信息；判断service信息中是否存在预设主从标签；若存在预设主从标签且预设主从标签的值为第一预设值，则触发查询pod ip列表中每个pod ip对应的pod信息的步骤。若不存在预设主从标签，或存在预设主从标签且预设主从标签的值为第二预设值，则不进行任何处理。
需要指出的是，endpoint名称即为service名称，因此，可以基于endpoint名称查询 service信息。并且，应用开发人员在为应用创建service时，可以根据是否有主从高可用的需求，为service添加一个标签即预设主从标签。在预设准入控制器中可以判断service是否有此标签，并针对有此标签的service，再去执行后续的主pod选择过程，并且，可以根据需求，通过对该标签配置不同的值，开启或关闭后续主pod选择过程，达到配置简单、不影响其他应用的效果。比如，第一预设值为true，第二预设值为false。
步骤S13：查询pod ip列表中每个pod ip对应的pod信息。
其中，pod信息可以包括创建时间、名称等。
步骤S14：基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod。
在一种实施方式中，可以基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最早的一个pod，作为主pod。可以理解的是，最早创建的pod比较稳定。
在另一种实施方式中，可以基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最晚的一个pod，作为主pod。可以理解的是，最晚创建的pod为基于最新应用程序创建的pod，便于提供更新的应用服务。
在具体的实施方式中，可以根据创建时间对全部pod进行排序，根据排序结果确定主pod。
当然，在一些实施例中，还可以通过其他策略确定主pod。
步骤S15：将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。
需要指出的是，本申请中，请求信息可以为全局变量，这样，预设准入控制器可以直接对请求信息进行修改。
其中，当k8s平台监测到目标应用的pod发生变化时，则发起endpoint更新请求；当目标应用中任一pod出现异常、或被删除、或新增了pod，则判定目标应用的pod发生变化。也即，本申请一些实施例在为service创建endpoint的过程中，调用预设准入控制器，根据当前endpoint创建请求中的所有pod ip，查询关联的pod信息，并根据预设策略从所有pod中筛选一个主pod，使用该pod的pod ip替换请求信息中的pod ip列表，从而实现通过service的请求流量只转发到该pod，该pod将作为主副本响应请求。当该应用对应的pod发生变化时，k8s会实时自动触发endpoint更新请求，同样会通过admission webhook机制调用预设准入控制器，基于创建endpoint时的同样逻辑再次选择新的pod作为主pod。这样，基于k8s的service/endpoint资源管理及adminssion webhook机制，通过开发webhook程序，在为 service创建或更新endpoint的过程中，根据预置的策略选择某一个pod ip作为endpoint中的pod ip，也即选择了一个pod作为service负载的后端，从而实现流量直接转发到该pod。这样，实现了多副本应用的主从高可用访问机制，无需应用自主开发主从选举机制，应用可以专注于应用本身业务逻辑，避免流量到从副本转发带来的性能问题，并且一次开发部署，可以给集群所有有需求的应用使用。整体方案简洁灵活，易于扩展，有新的pod选择策略直接修改控制器处理逻辑即可，具有良好的复用性和可扩展性。
例如，参见图2所示，图2为本申请一些实施例公开的一种具体的应用访问方案示意图。客户端发起创建service请求，并为service添加主从处理标签，以及将service的labelselector设置为应用的label。k8s接收到该请求，创建service，并根据labelselector查询该应用对应的所有pod，得到pod ip列表，进而确定请求信息，基于请求信息发起endpoint创建请求，并调用已注册好的admission controller(预设准入控制器)，在检测到有pod异常、删除、或新增，基于当前的请求信息自动发起endpoint更新请求，预设准入控制器的业务处理逻辑为：解析endpoint创建或更新请求，得到请求解析信息；从请求解析信息中获取endpoint名称、pod ip列表等；根据endpoint名称查询service信息；判断service是否存在主从标签，如果存在该标签并且值为true，说明该服务需要主从访问，则进行后续的处理逻辑，如果不存在该标签，说明该服务不需要主从访问，则不再继续执行，直接完成。后续的处理逻辑包括：根据pod ip列表查询所有pod信息，按创建时间由早到晚排序，获取第一个pod ip；用筛选出的pod ip替换原请求信息中的ip列表，以便k8基于更新的请求信息创建或者更新endpoint。
可见，本申请一些实施例先解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息，之后从请求解析信息中获取目标应用对应pod ip列表，并查询pod ip列表中每个pod ip对应的pod信息，然后基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod，最后将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。也即，本申请一些实施例通过预设准入控制器对k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求进行解析，得到请求解析信息，并基于请求解析信息和预设策略确定出一个主pod，利用该主pod的pod ip替换掉请求信息中的pod ip列表，k8s平台基于该请求信息创建或更新的endpoint，能够将目标应用的访问流量均转发至主pod上，避免了复杂且不易维护的选举机制，以及从副本的转发流量带来的性能问题，能够降低应用开发的复杂度，并且提升应用访问的响应性能。
参见图3所示，本申请一些实施例公开了一种应用访问装置，应用于预设准入控制器，包括：
请求解析模块11，用于解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；
列表获取模块12，用于从请求解析信息中获取目标应用对应pod ip列表；
信息查询模块13，用于查询pod ip列表中每个pod ip对应的pod信息；
主pod确定模块14，用于基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod；
信息更新模块15，用于将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建endpoint或更新，以将目标应用的访问流量均转发至主pod上。
可见，本申请一些实施例先解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息，之后从请求解析信息中获取目标应用对应pod ip列表，并查询pod ip列表中每个pod ip对应的pod信息，然后基于全部pod信息以及预设策略从目标应用的全部pod中确定出一个主pod，最后将请求信息中的pod ip列表替换为主pod的pod ip以得到替换后请求信息，以便k8s平台基于替换后请求信息创建或更新endpoint，以将目标应用的访问流量均转发至主pod上。也即，本申请一些实施例通过预设准入控制器对k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求进行解析，得到请求解析信息，并基于请求解析信息和预设策略确定出一个主pod，利用该主pod的pod ip替换掉请求信息中的pod ip列表，k8s平台基于该请求信息创建或更新的endpoint，能够将目标应用的访问流量均转发至主pod上，避免了复杂且不易维护的选举机制，以及从副本的转发流量带来的性能问题，能够降低应用开发的复杂度，并且提升应用访问的响应性能。
在本申请一些实施例中，应用访问装置还包括：endpoint名称获取模块，用于从请求解析信息中获取endpoint名称。
相应的，应用访问装置还包括：
service信息查询模块，用于基于endpoint名称查询service信息；其中，service信息为endpoint对应的service的信息；
主从标签判断模块，用于判断service信息中是否存在预设主从标签；若存在预设主从标签且预设主从标签的值为第一预设值，则触发信息查询模块13执行查询pod ip列表中每个 pod ip对应的pod信息的步骤。若不存在预设主从标签，或存在预设主从标签且预设主从标签的值为第二预设值，则不进行任何处理。
在一种实施方式中，主pod确定模块14，具体用于基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最早的一个pod，作为主pod。
在另一种实施方式中，主pod确定模块14，具体用于基于全部pod信息以及预设策略从目标应用的全部pod中确定出创建时间最晚的一个pod，作为主pod。
在本申请一些实施例中，应用访问装置还包括请求获取模块，用于基于admission webhook机制获取k8s平台发起的endpoint创建请求或endpoint更新请求。
参见图4所示，本申请一些实施例公开了一种电子设备20，包括处理器21和存储器22；其中，存储器22，用于保存计算机程序；处理器21，用于执行计算机程序，前述实施例公开的应用访问方法。
关于上述应用访问方法的具体过程可以参考前述实施例中公开的相应内容，在此不再进行赘述。
并且，存储器22作为资源存储的载体，可以是只读存储器、随机存储器、磁盘或者光盘等，存储方式可以是短暂存储或者永久存储。
另外，电子设备20还包括电源23、通信接口24、输入输出接口25和通信总线26；其中，电源23用于为电子设备20上的各硬件设备提供工作电压；通信接口24能够为电子设备20创建与外界设备之间的数据传输通道，其所遵循的通信协议是能够适用于本申请技术方案的任意通信协议，在此不对其进行具体限定；输入输出接口25，用于获取外界输入数据或向外界输出数据，其具体的接口类型可以根据具体应用需要进行选取，在此不进行具体限定。
进一步的，本申请一些实施例还公开了一种计算机非易失性可读存储介质，用于保存计算机程序，如图5所示，计算机非易失性可读存储介质5上存储有计算机程序51，其中，计算机程序51被处理器执行时实现前述实施例公开的应用访问方法。
关于上述应用访问方法的具体过程可以参考前述实施例中公开的相应内容，在此不再进行赘述。
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其它实施例的不同之处，各个实施例之间相同或相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即 可。
结合本文中所公开的实施例描述的方法或算法的步骤可以直接用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM，Random Access Memory)、内存、只读存储器(ROM,Read-Only Memory)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上对本申请所提供的一种应用访问方法、装置、设备及介质进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上，本说明书内容不应理解为对本申请的限制。

Claims (20)

  1. 一种应用访问方法，其特征在于，应用于预设准入控制器，包括：
    解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；
    从所述请求解析信息中获取目标应用对应pod ip列表；
    查询所述pod ip列表中每个pod ip对应的pod信息；
    基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出一个主pod；
    将所述请求信息中的所述pod ip列表替换为所述主pod的pod ip以得到替换后请求信息，以便所述k8s平台基于所述替换后请求信息创建或更新endpoint，以将所述目标应用的访问流量均转发至所述主pod上。
  2. 根据权利要求1所述的应用访问方法，其特征在于，所述请求信息包括k8s平台查找到的目标应用的所有pod的pod ip，以及待创建或待更新endpoint的endpoint名称。
  3. 根据权利要求1所述的应用访问方法，其特征在于，还包括：
    从所述请求解析信息中获取endpoint名称；
    相应的，在所述查询所述pod ip列表中每个pod ip对应的pod信息之前，还包括：
    基于所述endpoint名称查询service信息；其中，所述service信息为所述endpoint对应的service的信息；
    判断所述service信息中是否存在预设主从标签；
    若存在所述预设主从标签且所述预设主从标签的值为第一预设值，则触发所述查询所述pod ip列表中每个pod ip对应的pod信息的步骤。
  4. 根据权利要求3所述的应用访问方法，其特征在于，还包括：
    若不存在所述预设主从标签，或存在所述预设主从标签且所述预设主从标签的值为第二预设值，则不进行任何处理。
  5. 根据权利要求3所述的应用访问方法，其特征在于，所述endpoint名称为service名称。
  6. 根据权利要求3所述的应用访问方法，其特征在于，所述预设主从标签经由客户端在向k8s平台发起创建service请求时为service进行添加。
  7. 根据权利要求1所述的应用访问方法，其特征在于，所述pod信息包括创建时 间、名称。
  8. 根据权利要求7所述的应用访问方法，其特征在于，所述基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出一个主pod，包括：
    基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出创建时间最早的一个pod，作为主pod。
  9. 根据权利要求7所述的应用访问方法，其特征在于，所述基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出一个主pod，包括：
    基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出创建时间最晚的一个pod，作为主pod。
  10. 根据权利要求7所述的应用访问方法，其特征在于，所述基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出一个主pod，包括：
    根据所述pod信息中的创建时间对全部pod进行排序，根据排序结果确定主pod。
  11. 根据权利要求1至9任一项所述的应用访问方法，其特征在于，所述解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求之前，还包括：
    基于admission webhook机制获取k8s平台发起的所述endpoint创建请求或endpoint更新请求。
  12. 根据权利要求1至9任一项所述的应用访问方法，其特征在于，所述endpoint更新请求基于k8s平台监测到目标应用的pod发生变化时发起；所述目标应用的pod发生变化基于目标应用中任一pod出现异常或被删除、或新增pod的情况判定。
  13. 根据权利要求1至9任一项所述的应用访问方法，其特征在于，所述预设准入控制器部署在容器平台上，所述预设准入控制器基于k8s平台的service、endpoint资源管理并结合webhook机制开发得到。
  14. 根据权利要求13所述的应用访问方法，其特征在于，还包括：
    在k8s平台创建endpoint时，调用预设准入控制器，并将endpoint创建请求传入预设准入控制器。
  15. 根据权利要求13所述的应用访问方法，其特征在于，还包括：
    在为service创建endpoint的过程中，调用预设准入控制器，根据当前endpoint创建请求中的所有pod ip，查询关联的pod信息；
    根据预设策略从所有pod中筛选一个主pod，使用该pod的pod ip替换请求信息中的pod ip列表，以实现通过service的请求流量只转发到该pod，该pod将作为主副本响应请求。
  16. 根据权利要求14或15所述的应用访问方法，其特征在于，所创建的endpoint为所述k8s平台在每创建一个service后，实时创建同名的endpoint资源，所述endpoint资源包含service所要负载的所有pod ip和端口。
  17. 一种应用访问装置，其特征在于，应用于预设准入控制器，包括：
    请求解析模块，用于解析k8s平台基于请求信息发起的endpoint创建请求或endpoint更新请求以得到请求解析信息；
    列表获取模块，用于从所述请求解析信息中获取目标应用对应pod ip列表；
    信息查询模块，用于查询所述pod ip列表中每个pod ip对应的pod信息；
    主pod确定模块，用于基于全部所述pod信息以及预设策略从所述目标应用的全部pod中确定出一个主pod；
    信息更新模块，用于将所述请求信息中的所述pod ip列表替换为所述主pod的pod ip以得到替换后请求信息，以便所述k8s平台基于所述替换后请求信息创建或更新endpoint，以将所述目标应用的访问流量均转发至所述主pod上。
  18. 根据权利要求17所述的应用访问装置，其特征在于，还包括：
    endpoint名称获取模块，用于从所述请求解析信息中获取endpoint名称；
    service信息查询模块，用于基于所述endpoint名称查询service信息；其中，所述service信息为所述endpoint对应的service的信息；
    主从标签判断模块，用于判断所述service信息中是否存在预设主从标签；若存在所述预设主从标签且所述预设主从标签的值为第一预设值，则触发所述信息查询模块执行所述查询所述pod ip列表中每个pod ip对应的pod信息的步骤。
  19. 一种电子设备，其特征在于，包括处理器和存储器；其中，
    所述存储器，用于保存计算机程序；
    所述处理器，用于执行所述计算机程序以实现如权利要求1至16任一项所述的应用访问方法。
  20. 一种计算机非易失性可读存储介质，其特征在于，用于保存计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至16任一项所述的应用访问方法。
PCT/CN2023/084815 2022-04-11 2023-03-29 一种应用访问方法、装置、设备及介质 Ceased WO2023197874A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210371384.2 2022-04-11
CN202210371384.2A CN114448895B (zh) 2022-04-11 2022-04-11 一种应用访问方法、装置、设备及介质

Publications (1)

Publication Number Publication Date
WO2023197874A1 true WO2023197874A1 (zh) 2023-10-19

Family

ID=81360394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084815 Ceased WO2023197874A1 (zh) 2022-04-11 2023-03-29 一种应用访问方法、装置、设备及介质

Country Status (2)

Country Link
CN (1) CN114448895B (zh)
WO (1) WO2023197874A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120804761A (zh) * 2025-09-05 2025-10-17 中移(苏州)软件技术有限公司 一种Pod的标签标记方法、装置、设备、介质和产品

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114448895B (zh) * 2022-04-11 2022-06-17 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质
CN115277652B (zh) * 2022-06-29 2024-03-22 北京百度网讯科技有限公司 基于推理服务的流媒体处理方法、装置、电子设备
CN116170188A (zh) * 2022-12-30 2023-05-26 北京云思智学科技有限公司 网络访问控制方法、装置、电子设备和存储介质
CN116033010B (zh) * 2023-02-16 2024-10-29 北京有竹居网络技术有限公司 远程访问方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153143A (zh) * 2020-09-24 2020-12-29 新浪网技术(中国)有限公司 Kubernetes集群的流量调度方法、装置及电子设备
WO2021063339A1 (zh) * 2019-09-30 2021-04-08 星环信息科技(上海)股份有限公司 集群资源调度方法、装置、设备及储存介质
US20210328858A1 (en) * 2020-04-16 2021-10-21 Ribbon Communications Operating Company, Inc. Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system
CN114124948A (zh) * 2021-09-19 2022-03-01 济南浪潮数据技术有限公司 一种云端组件高可用的方法、装置、设备及可读介质
CN114448895A (zh) * 2022-04-11 2022-05-06 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113741923A (zh) * 2020-05-27 2021-12-03 华为技术有限公司 一种应用更新方法、装置、设备及介质
CN111901157B (zh) * 2020-07-10 2023-01-10 苏州浪潮智能科技有限公司 一种基于k8s的服务部署方法、装置、设备、介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021063339A1 (zh) * 2019-09-30 2021-04-08 星环信息科技(上海)股份有限公司 集群资源调度方法、装置、设备及储存介质
US20210328858A1 (en) * 2020-04-16 2021-10-21 Ribbon Communications Operating Company, Inc. Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system
CN112153143A (zh) * 2020-09-24 2020-12-29 新浪网技术(中国)有限公司 Kubernetes集群的流量调度方法、装置及电子设备
CN114124948A (zh) * 2021-09-19 2022-03-01 济南浪潮数据技术有限公司 一种云端组件高可用的方法、装置、设备及可读介质
CN114448895A (zh) * 2022-04-11 2022-05-06 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120804761A (zh) * 2025-09-05 2025-10-17 中移(苏州)软件技术有限公司 一种Pod的标签标记方法、装置、设备、介质和产品

Also Published As

Publication number Publication date
CN114448895A (zh) 2022-05-06
CN114448895B (zh) 2022-06-17

Similar Documents

Publication Publication Date Title
WO2023197874A1 (zh) 一种应用访问方法、装置、设备及介质
US10630779B2 (en) System and method for using VoIP session continuity information using logical scalable units
US10523545B2 (en) System and method for managing VoIP session continuity information using logical scalable units
US11157304B2 (en) System for peering container clusters running on different container orchestration systems
US12423157B2 (en) Systems and methods providing serverless DNS integration
US7779010B2 (en) Repartitioning live data
US11991094B2 (en) Metadata driven static determination of controller availability
CN102012944B (zh) 一种提供复制特性的分布式nosql数据库的实现方法
CN109819055B (zh) 一种同时支持Ribbon和Eureka实现负载均衡的方法
EP3583765B1 (en) Endpoint abstraction for service-to-service communication
WO2024193269A1 (zh) 数据库访问方法、装置及计算机可读存储介质
US11768704B2 (en) Increase assignment effectiveness of kubernetes pods by reducing repetitive pod mis-scheduling
WO2025123783A1 (zh) 云盘管控方法、系统、电子设备及存储介质
US12580811B2 (en) Highly scalable container network interface operation to reduce startup overhead of functions
CN109525590B (zh) 数据包的传输方法及装置
US20210377718A1 (en) Pattern affinity for discovery
US20240031265A1 (en) Use of custom resource definitions for reporting network resource usage of a node cluster
US11711315B1 (en) Dynamic endpoint resources discovery in Kubernetes clusters via stable URI locator for workflow services
EP3065379A1 (en) System and method for volte session continuation using logical scalable units
US10693705B2 (en) Show command service aka CLI relay
EP4529137B1 (en) Udp message distribution method, device and readable storage medium
US20240259473A1 (en) Distributed serverless rule consequence evaluation for a containerized rules engine
EP4538884A1 (en) Inheritance operator for managing a plurality of service versions within a cluster
WO2021072967A1 (zh) 一种配置信息管理方法及装置
CN112583740A (zh) 网络通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23787520

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11/03/2025)

122 Ep: pct application non-entry in european phase

Ref document number: 23787520

Country of ref document: EP

Kind code of ref document: A1