Abstract: A volume management server may regularly check the status of persistent volumes to determine if they have been released. A database with information about the persistent volumes may be updated to indicate a current date as the release date when a persistent volume is found to be released without a release date. This enables the volume management server to determine, in the future, how long the persistent volume has been released. When the difference between the current date and the release date for a persistent volume reaches a first predetermined age threshold, the volume management server notifies a set of users. When the difference between the current date and the release date for the persistent volume reaches a second predetermined age threshold, the volume management server causes deletion of the persistent volume.

Abstract: Methods, systems, and computer-readable storage media for executing a load balancer optimization engine for a cluster that includes a set of nodes, a first sub-set of nodes being used for load balancing by one or more external load balancers, a second sub-set of nodes being excluded from load balancing, determining, by the load balancer optimization engine, a delta value based on a pool count and a number of nodes in a candidate node list, transmitting, by the load balancer optimization engine, a request to adjust a number of nodes in the first sub-set of nodes and a number of nodes in the second sub-set of nodes responsive to the delta value, and adjusting, by a cloud controller of the cluster, the number nodes in the first sub-set of nodes by the delta value and a number of nodes in the second sub-set of nodes by the to the delta value.

Abstract: A computer-implemented method may comprise obtaining thresholds for metrics for microservices, injecting metadata comprising the thresholds for each microservice into a pod within which the microservice is running, obtaining the metrics for the microservices, obtaining the corresponding metadata from the pod within which each microservice is running, determining that one of the thresholds for one of the microservices has been violated using the metadata of the microservice obtained from the corresponding pod of the microservice and the corresponding set of metrics for the microservice, and sending an alert to an electronic destination based on the determining that the threshold for the microservice has been violated. The alert may indicate that the threshold for the microservice has been violated.

Abstract: Briefly, embodiments of a system, method, and article for scanning a database for a containerized environment to acquire information for a set of containers for applications. The information may include at least namespace associations and metadata for individual containers of the set of containers. One or more orphan containers may be detected within the set of containers for applications, where the one or more orphan containers may be associated with unknown owner information. Defined rules may be applied to determine owner information for at least one of the one or more orphan containers based at least in part on the namespace associations and metadata for the at least one of the one or more orphan containers. The determined owner information for the at least one of the one or more orphan containers may be stored in a storage device.

Abstract: A volume management server may regularly check the status of persistent volumes to determine if they have been released. A database with information about the persistent volumes may be updated to indicate a current date as the release date when a persistent volume is found to be released without a release date. This enables the volume management server to determine, in the future, how long the persistent volume has been released. When the difference between the current date and the release date for a persistent volume reaches a first predetermined age threshold, the volume management server notifies a set of users. When the difference between the current date and the release date for the persistent volume reaches a second predetermined age threshold, the volume management server causes deletion of the persistent volume.

Abstract: A computer-implemented method may comprise obtaining thresholds for metrics for microservices, injecting metadata comprising the thresholds for each microservice into a pod within which the microservice is running, obtaining the metrics for the microservices, obtaining the corresponding metadata from the pod within which each microservice is running, determining that one of the thresholds for one of the microservices has been violated using the metadata of the microservice obtained from the corresponding pod of the microservice and the corresponding set of metrics for the microservice, and sending an alert to an electronic destination based on the determining that the threshold for the microservice has been violated. The alert may indicate that the threshold for the microservice has been violated.