Autoscaling

The VerticaAutoscaler provides flexible scaling options, allowing you to scale specific subclusters or the entire database. You can scale a specific subcluster or a subset of subclusters by specifying a service name, or scale the entire database by leaving the service name empty, which scales across all nodes. This section explains two ways to scale the database. You can use the Horizontal Pod Autoscaler (HPA), which is a core Kubernetes feature that scales based on CPU and memory usage (it can also use custom metrics like Prometheus, but this often requires additional configuration), or KEDA’s ScaledObject for Prometheus-based scaling, which scales based on Prometheus metrics. For OpenShift, using KEDA’s ScaledObject is recommended due to HPA limitations in OpenShift. The following sections detail how to configure and deploy both autoscalers to scale an entire database, setup instructions for OpenShift environments, use cases, and best practices.