Horizontal Scaling

Horizontal scaling for the Kubernetes Cluster is represented via two implementations:

  • CirrusGrid-managed horizontal scaling – allows adding/removing Kubernetes nodes. Based on your needs, you can configure scaling triggers to automate this process based on resource utilization.
  • Kubernetes-managed Horizontal Pod Autoscaler – scales deployments up/down based on observed CPU utilization

With both of these horizontal scaling methods, Kubernetes Cluster always has nodes available (when needed) and healthy application pods.

Tip: An extended real case example (WordPress) on the Kubernetes Cluster Scaling is provided within the linked article.

Powered by BetterDocs