Cluster autoscaling

One benefit of deploying ArcGIS Enterprise on Kubernetes is that you can configure the cluster to automatically change the amount of compute resources you have available in response to changing needs. When demand is high, the cluster autoscaler adds new nodes to the cluster to meet that demand. When demand is low, the autoscaler removes nodes from the cluster to reduce costs.

To take advantage of autoscaling, you must deploy ArcGIS Enterprise on a cluster that uses one of the supported autoscalers:

• Kubernetes Cluster Autoscaler is the traditional autoscaler. It is well integrated with many managed cloud services and is supported for any cluster where ArcGIS Enterprise on Kubernetes can be deployed.

  Refer to your cluster provider's documentation for information on implementing Kubernetes Cluster Autoscaler.

• Karpenter is a newer autoscaler designed to quickly provision nodes that match the needs of pending workloads. Karpenter must be enabled on the cluster before deploying ArcGIS Enterprise, and is supported for AKS and EKS clusters.

  To deploy ArcGIS Enterprise on a cluster that uses the Karpenter autoscaler, it is recommended that you use your cloud provider's managed Karpenter implementation. For instructions, see the ArcGIS Enterprise deployment guides for EKS Auto Mode and AKS Node Auto-Provisioning (NAP).