Resource scheduling method and device, electronic equipment and storage medium
By using Admission Controller to create Namespaces and accounts for tenants in the Kubernetes platform, dynamically adjusting resource requests and restrictions, the problem of lack of flexibility and dynamic adjustment capabilities of resource scheduling solutions in the existing technology is solved, and efficient resource utilization and between tenants is achieved. Isolation meets the convenient and efficient needs of modern enterprises.
Patent Information
- Application Number
- CN202411141345.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-20
- Publication Date
- 2024-11-22
AI Technical Summary
The existing resource scheduling scheme lacks flexibility in a multi-tenant environment and cannot dynamically adjust resource allocation, resulting in low resource utilization efficiency, waste of manpower and material resources, and cannot meet the convenient and efficient needs of modern enterprises.
Use Admission Controller to create Namespace for tenants in the Kubernetes platform and generate corresponding accounts. By dynamically adjusting resource requests and restrictions, efficient resource utilization and resource isolation between tenants can be achieved.
It realizes flexible allocation and management of resources, improves resource utilization efficiency, meets the convenience and efficiency needs of modern enterprises, simplifies the resource scheduling process, and has a wider scope of application.
Smart Images

Figure CN119003091A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of cloud computing technology, and in particular to a resource scheduling method, device, electronic device and storage medium. Background Art
[0002] In recent years, Kubernetes has become increasingly popular in enterprises, and resource scheduling and allocation have become an important requirement in a multi-tenant environment. How to conveniently and quickly schedule resources to meet the needs of different tenants has become a difficult problem faced by all Kubernetes administrators.
[0003] At present, most resource scheduling solutions on the market require the use of predefined policies and configuration files, which greatly limits the flexibility of scheduling, and cannot know the resource usage in advance and has no ability to dynamically adjust, making it impossible to manage resources efficiently, resulting in a large waste of manpower and material resources. With cloud computing and automation so common today, traditional resource scheduling methods can no longer meet the convenience needs of today's enterprises. More developers and operation and maintenance personnel are willing to use a simpler and more convenient method to complete resource scheduling and management. Summary of the invention
[0004] The present application provides a resource scheduling method, device, electronic device and storage medium. By using AdmissionController, resource allocation and management in a Kubernetes multi-tenant environment can be flexibly implemented. By dynamically adjusting resource requests and restrictions, efficient resource utilization and resource isolation between tenants are ensured, meeting the needs of modern enterprises for convenience and efficiency.
[0005] In a first aspect, an embodiment of the present application provides a resource scheduling method, the method comprising:
[0006] Receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and a resource requirement;
[0007] In response to the service deployment request, a Namespace is created for the tenant through an Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant deploys an application under the account corresponding to the Namespace in the Kubernetes platform.
[0008] In a second aspect, an embodiment of the present application further provides a resource scheduling device, the device comprising: a receiving module and a creating module; wherein:
[0009] The receiving module is used to receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and a resource requirement;
[0010] The creation module is used to create a Namespace for the tenant through the Admission Controller in response to the service deployment request, and generate an account corresponding to the Namespace for the tenant, so that the tenant deploys the application under the account corresponding to the Namespace in the Kubernetes platform.
[0011] In a third aspect, an embodiment of the present application provides an electronic device, including:
[0012] one or more processors;
[0013] a memory for storing one or more programs,
[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement the resource scheduling method described in any embodiment of the present application.
[0015] In a fourth aspect, an embodiment of the present application provides a storage medium on which a computer program is stored, and when the program is executed by a processor, the resource scheduling method described in any embodiment of the present application is implemented.
[0016] The embodiment of the present application proposes a resource scheduling method, device, electronic device and storage medium, which first receives a service deployment request sent by a tenant; wherein the service deployment request includes: the tenant name and project name and the resource demand; then, in response to the service deployment request, a Namespace is created for the tenant through the Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant deploys the application under the account corresponding to the Namespace in the Kubernetes platform. That is to say, in the technical solution of the present application, a Namespace can be created for the tenant through the Admission Controller, and an account corresponding to the Namespace can be generated for the tenant, ensuring that the Namespace of the tenant is isolated from the Namespaces of other tenants. In the prior art, most resource scheduling solutions on the market require the use of predefined strategies and configuration files, which greatly limits the flexibility of scheduling, and it is impossible to know the usage of resources in advance and there is no ability to dynamically adjust, so it is impossible to efficiently manage resources, resulting in a large amount of waste of manpower and material resources. Therefore, compared with the prior art, the resource scheduling method, device, electronic device and storage medium proposed in the embodiments of the present application can flexibly implement resource allocation and management in a Kubernetes multi-tenant environment by using AdmissionController, and ensure efficient utilization of resources and resource isolation between tenants by dynamically adjusting resource requests and restrictions, thereby meeting the needs of modern enterprises for convenience and efficiency; moreover, the technical solution of the embodiments of the present application is simple and convenient to implement, easy to popularize, and has a wider scope of application. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 A schematic diagram of a resource scheduling method according to an embodiment of the present application;
[0018] Figure 2 A schematic diagram of a flow chart of a resource scheduling method provided in another embodiment of the present application;
[0019] Figure 3 A schematic diagram of the structure of a resource scheduling device provided in one embodiment of the present application;
[0020] Figure 4 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0021] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only the parts related to the present application, rather than all structures, are shown in the accompanying drawings.
[0022] Figure 1 This is a flow chart of a resource scheduling method provided by an embodiment of the present application. The method can be executed by a resource scheduling device or electronic device. The device or electronic device can be implemented by software and / or hardware. The device or electronic device can be integrated in any intelligent device with network communication function. Figure 1 As shown, the resource scheduling method may include the following steps:
[0023] S101. Receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and resource requirements.
[0024] In this step, the service deployment request sent by the tenant can be received through the Kubernetes platform. Kubernetes is an open source container orchestration platform for automating the deployment, expansion and management of containerized applications. Kubernetes provides the following main functions: 1) Service discovery and load balancing: Kubernetes can provide internal IP addresses for containers and perform load balancing between container instances. It can also expose services to the external network and access these services through DNS names or their own IP addresses. 2) Storage orchestration: Kubernetes allows the mounting of read-write separated storage systems for containers to use. 3) Automatic deployment and rollback: Kubernetes can be used to describe the desired state of a deployment. If the actual state does not match the desired state, Kubernetes will try to make the actual state consistent with the desired state. 4) Automatic packaging and self-healing: Kubernetes will place containers on the best nodes to run based on CPU and memory indicators. If the container fails, Kubernetes will restart the container or reschedule it on other nodes. 5) Key and configuration management: Kubernetes allows users to store and manage sensitive information as secret objects, so that access to this information can be controlled without changing the application code. 6) Batch processing: Kubernetes supports batch / queue tasks, such as MapReduce or Hadoop jobs. 7) Microservice architecture support: Kubernetes is an ideal platform for building and running microservices because it can help manage multiple containerized services and ensure smooth communication between them. 8) Multi-tenant support: Kubernetes can be configured to support a multi-user environment, where each user can have their own namespace in the cluster.
[0025] S102. In response to the service deployment request, a Namespace is created for the tenant through the Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant deploys an application under the account corresponding to the Namespace in the Kubernetes platform.
[0026] Admission Controller is an important component in Kubernetes, which allows requests to be intercepted and processed before they reach the API server and are persisted to etcd storage. Admission Controller can be used to enforce various policies, such as resource quota management, default value setting, security policy enforcement, object conversion, etc., to help ensure the stability and security of the cluster.
[0027] In Kubernetes, Namespace is a mechanism for dividing cluster resources. It provides the ability to group cluster resources into different virtual clusters, even if they are actually running on the same physical or virtual cluster. Namespace is particularly useful for large organizations and can be used to isolate different teams, projects, environments, or customers to achieve the following purposes: 1) Resource isolation: Namespace allows users to separate resources (such as Pods, Services, ConfigMaps, etc.) so that resources from different teams or projects do not conflict. Resource names within each Namespace can be repeated as long as they are in different Namespaces. There will be no conflict. 2) Permission control: You can set independent access control policies for each Namespace, which means that different users or teams can be assigned access rights to a specific Namespace without having to grant these users access to the entire cluster. 3) Resource quotas: You can set resource quotas for each Namespace to limit the amount of CPU, memory, and other resources that can be used within the Namespace. This helps prevent excessive consumption and abuse of resources. 4) Simplified resource management: In a large cluster, Namespace can help users better organize and manage resources. By placing related resources under the same Namespace, it is easier to view and control these resources. 5) Environment isolation: Namespace can be used to distinguish different environments, such as development, test, and production environments, to ensure that they do not interfere with each other. 6) Multi-tenant support: In a multi-tenant environment, each tenant can have its own Namespace, thereby achieving resource isolation and independent management.
[0028] The resource scheduling method proposed in the embodiment of the present application first receives a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name and a project name and resource demand; then, in response to the service deployment request, a Namespace is created for the tenant through the Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant can deploy an application under the account corresponding to the Namespace in the Kubernetes platform. That is to say, in the technical solution of the present application, a Namespace can be created for the tenant through the Admission Controller, and an account corresponding to the Namespace can be generated for the tenant, ensuring that the Namespace of the tenant is isolated from the Namespace of other tenants. In the prior art, most resource scheduling solutions on the market require the use of predefined strategies and configuration files, which greatly limits the flexibility of scheduling, and it is impossible to know the usage of resources in advance and there is no ability to dynamically adjust, so it is impossible to efficiently manage resources, resulting in a large amount of waste of manpower and material resources. Therefore, compared with the prior art, the resource scheduling method proposed in the embodiment of the present application can flexibly implement resource allocation and management in a Kubernetes multi-tenant environment by using the Admission Controller, and ensure efficient resource utilization and resource isolation between tenants by dynamically adjusting resource requests and restrictions, thereby meeting the needs of modern enterprises for convenience and efficiency; moreover, the technical solution of the embodiment of the present application is simple and convenient to implement, easy to popularize, and has a wider scope of application.
[0029] Figure 2 This is a flow chart of a resource scheduling method provided by another embodiment of the present application. It is further optimized and expanded based on the above technical solution and can be combined with the above optional implementation methods. Figure 2 As shown, the resource scheduling method may include the following steps:
[0030] S201. Receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and resource requirements.
[0031] S202. In response to the service deployment request, a Namespace is created for the tenant through the Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant deploys the application under the account corresponding to the Namespace in the Kubernetes platform.
[0032] S203. Receive, through the Kubernetes platform, a deployment template in a predetermined format sent by the tenant.
[0033] In Kubernetes, receiving and processing a deployment template in a predetermined format sent by a tenant usually involves the following steps: 1) Define template specifications: First, you need to define a standard template format that tenants can use. This is usually a YAML or JSON file that describes Kubernetes resources such as Deployments, Services, ConfigMaps, etc. The template should contain sufficient metadata, such as labels and annotations, to facilitate subsequent processing and classification. 2) Create an API endpoint: In order to receive requests from tenants, you need to create an API endpoint in the Kubernetes cluster or an external system. This endpoint will be responsible for receiving the uploaded template file and triggering subsequent processing. 3) Template validation: After receiving the template, it needs to be validated to ensure that it conforms to the predefined format and rules. This can be done by parsing YAML or JSON and checking its structure. Kubernetes client libraries (such as kubernetes-client) can be used to help verify whether the resources are legal. 4) Permission and quota checks: Before processing the template, you need to confirm that the tenant has the permission to create or update resources in the target Namespace and that the creation of resources will not violate any quota restrictions. 5) Template conversion and customization: If necessary, the template can be converted or customized according to the specific needs of the tenant or the configuration of the cluster. For example, it may be necessary to inject default environment variables, tags or configurations, or adjust resource requests and limits.
[0034] S204. Send the resource list corresponding to the deployment template to the WebHook of the Admission Controller through the API Server of the Kubernetes platform, so that the WebHook adds node affinity for the application in the resource list based on the Namespace to which the Pod resource belongs, and returns the resource list with added node affinity to the API Server.
[0035] In this step, we use Webhook to dynamically add node affinity based on the Namespace to which the Pod resource belongs in Kubernetes, which can implement a more fine-grained resource scheduling strategy. Node affinity is a scheduling strategy that allows you to decide whether a Pod can be scheduled to a certain node based on the node's label. This strategy can be used in many scenarios such as optimizing resource usage, isolating environments, and regional affinity.
[0036] S205. The scheduler of the Kubernetes platform adds a resource list with node affinity and allocates the application to the account corresponding to the Namespace.
[0037] S206. Update the selected node information into the deployment template through the scheduler of the Kubernetes platform, and return the deployment template with the updated selected node information to the API Server.
[0038] S207, notifying the management program Kubelet on the selected node of the allocated Pod information through the API Server, so that after receiving the Pod information, the Kubelet on the selected node pulls the required image according to the definition of the Pod information and starts the container on the selected node.
[0039] In a specific embodiment of the present application, a label may be added to the Namespace of a tenant so that the Namespace of the tenant is isolated from the Namespaces of other tenants.
[0040] The resource scheduling method proposed in the embodiment of the present application first receives a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name and a project name and resource demand; then, in response to the service deployment request, a Namespace is created for the tenant through the Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant can deploy an application under the account corresponding to the Namespace in the Kubernetes platform. That is to say, in the technical solution of the present application, a Namespace can be created for the tenant through the Admission Controller, and an account corresponding to the Namespace can be generated for the tenant, ensuring that the Namespace of the tenant is isolated from the Namespace of other tenants. In the prior art, most resource scheduling solutions on the market require the use of predefined strategies and configuration files, which greatly limits the flexibility of scheduling, and it is impossible to know the usage of resources in advance and there is no ability to dynamically adjust, so it is impossible to efficiently manage resources, resulting in a large amount of waste of manpower and material resources. Therefore, compared with the prior art, the resource scheduling method proposed in the embodiment of the present application can flexibly implement resource allocation and management in a Kubernetes multi-tenant environment by using the Admission Controller, and ensure efficient resource utilization and resource isolation between tenants by dynamically adjusting resource requests and restrictions, thereby meeting the needs of modern enterprises for convenience and efficiency; moreover, the technical solution of the embodiment of the present application is simple and convenient to implement, easy to popularize, and has a wider scope of application.
[0041] Figure 3 This is a schematic diagram of the structure of a resource scheduling device provided in an embodiment of the present application. Figure 3 As shown, the resource scheduling device includes: a receiving module 301 and a creating module 302; wherein,
[0042] The receiving module 301 is used to receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and a resource requirement;
[0043] The creation module 302 is used to create a Namespace for the tenant through the Admission Controller in response to the service deployment request, and generate an account corresponding to the Namespace for the tenant, so that the tenant deploys the application under the account corresponding to the Namespace in the Kubernetes platform.
[0044] The resource scheduling device can execute the method provided by any embodiment of the present application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, please refer to the resource scheduling method provided by any embodiment of the present application.
[0045] Figure 4 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. Figure 4 A block diagram of an exemplary electronic device suitable for implementing the embodiments of the present application is shown. Figure 4 The electronic device 12 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0046] like Figure 4 As shown, the electronic device 12 is in the form of a general purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).
[0047] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
[0048] The electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.
[0049] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 not shown, usually called a "hard drive"). Although Figure 4 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical medium) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present application.
[0050] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described herein.
[0051] The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 12, and / or may communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. Furthermore, the electronic device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via the bus 18. It should be understood that although Figure 4 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0052] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the resource scheduling method provided in the embodiment of the present application.
[0053] The embodiment of the present application also provides a computer storage medium.
[0054] The computer-readable storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, - but not limited to - a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive lists) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, a device or a device or used in combination with it.
[0055] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0056] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0057] Computer program code for performing the operation of the present application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).
[0058] The embodiment of the present application also provides a computer program product.
[0059] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer program products, which can include one or more computer programs, which can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor, which can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0060] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims
1. A resource scheduling method, It is characterized in that The method comprises: Receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and a resource requirement; In response to the service deployment request, a Namespace is created for the tenant through an Admission Controller, and an account corresponding to the Namespace is generated for the tenant, so that the tenant deploys an application under the account corresponding to the Namespace in the Kubernetes platform.
2. The method according to claim 1, It is characterized in that The method further comprises: Receiving, through the Kubernetes platform, a deployment template in a predetermined format sent by the tenant; The resource list corresponding to the deployment template is sent to the WebHook of the Admission Controller through the API Server of the Kubernetes platform, so that the WebHook adds node affinity for the application in the resource list based on the Namespace to which the Pod resource belongs, and returns the resource list with the node affinity added to the API Server.
3. The method according to claim 2, It is characterized in that Before sending the resource list corresponding to the deployment template to the WebHook of the Admission Controller through the API Server of the Kubernetes platform, the method further includes: Check whether the Namespace has started the Admission Controller through the API Server; If the Namespace has started the Admission Controller, an operation of sending the resource list corresponding to the deployment template to the WebHook of the Admission Controller through the API Server of the Kubernetes platform is performed.
4. The method according to claim 3, It is characterized in that The method further comprises: The resource list with the node affinity added is used by the scheduler of the Kubernetes platform to allocate the application to the account corresponding to the Namespace.
5. The method according to claim 4, It is characterized in that The method further comprises: The selected node information is updated into the deployment template through the scheduler of the Kubernetes platform, and the deployment template for updating the selected node information is returned to the API Server.
6. The method according to claim 5, It is characterized in that The method further comprises: The API Server notifies the management program Kubelet on the selected node of the allocated Pod information, so that after receiving the Pod information, the Kubelet on the selected node pulls the required image according to the definition of the Pod information and starts the container on the selected node.
7. The method according to claim 1, It is characterized in that The method further comprises: A label is added to the namespace of the tenant so that the namespace of the tenant is isolated from the namespaces of other tenants.
8. A resource scheduling device, It is characterized in that The device comprises: a receiving module and a creating module; wherein, The receiving module is used to receive a service deployment request sent by a tenant; wherein the service deployment request includes: a tenant name, a project name, and a resource requirement; The creation module is used to create a Namespace for the tenant through the Admission Controller in response to the service deployment request, and generate an account corresponding to the Namespace for the tenant, so that the tenant deploys the application under the account corresponding to the Namespace in the Kubernetes platform.
9. An electronic device, It is characterized in that include: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the resource scheduling method according to any one of claims 1 to 7.
10. A storage medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the resource scheduling method according to any one of claims 1 to 7 is implemented.
