Dynamic horizontal autoscaling for multi-tenant service

A system comprising:

• a memory;
• and
• a processing device coupled to the memory, the processing device configured to execute instructions to:
• configure a network computing element to route a plurality of requests from two or more clients to a service in a containerized-networked system;
• monitor, by a horizontal service-level autoscaler, one or more aspects of the requests to the service from the two or more clients received through the network computing element between the two or more clients and the service;
• create a new pod comprising a set of running containers with shared resources in the containerized-networked system based at least in part on the horizontal service-level autoscaler determining that at least one of the one or more aspects of the requests exceeds a threshold;
• create a new service mapping to accept subsequent requests from one of the two or more clients that triggered creation of the new pod;
• and
• update routing rules in the network computing element to map the subsequent requests from the two or more clients using the new service mapping, wherein the new service mapping updates a service-to-pod mapping that is configurable to route the subsequent requests to shared pods and dedicated pods.

A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by one or more processors to cause the one or more processors to perform operations comprising:

• configuring a network computing element to route a plurality of requests from two or more clients to a service in a containerized-networked system;
• monitoring, by a horizontal service-level autoscaler, one or more aspects of the requests to the service from the two or more clients received through the network computing element between the two or more clients and the service;
• creating a new pod comprising a set of running containers with shared resources in the containerized-networked system, the creating based at least in part on the horizontal service-level autoscaler determining that at least one of the one or more aspects of the requests exceeds a threshold;
• creating a new service mapping to accept subsequent requests from the one or more clients that triggered creation of the new pod;
• and
• updating routing rules in the network computing element to map the subsequent requests from the two or more clients using the new service mapping, wherein the new service mapping updates a service-to-pod mapping that is configurable to route the subsequent requests to shared pods and dedicated pods.