cluster-proportional-autoscaler
Overprovisioner
cluster-proportional-autoscaler | Overprovisioner | |
---|---|---|
3 | 1 | |
589 | - | |
0.8% | - | |
5.8 | - | |
16 days ago | - | |
Go | ||
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cluster-proportional-autoscaler
-
Practical Introduction to Kubernetes Autoscaling Tools with Linode Kubernetes Engine
The Cluster Proportional Autoscaler (CPA) is a horizontal pod autoscaler that scales replicas based on the number of nodes in the cluster. Unlike other autoscalers, it does not rely on the Metrics API and does not require the Metrics Server. Additionally, unlike other autoscalers we saw, a CPA is not scaled with a Kubernetes resource but instead uses flags to identify target workloads and a ConfigMap for scaling configuration. The following diagram illustrates the components of the CPA:
-
K8s ephemeral application environments
Namespacing each environment would give you isolation, depending on how your service discovery works within the environment. You could consider the horizontal proportional autoscaler (or maybe KEDA) and hook it up to a metric for the queue depth. https://github.com/kubernetes-sigs/cluster-proportional-autoscaler
-
Kubernetes Cluster Over-Provisioning: Proactive App Scaling
If we want to configure dynamic overprovisioning of a cluster (e.g. 20% of resources in the cluster) then we need to use Horizontal Cluster Proportional Autoscaler.
Overprovisioner
-
Kubernetes Cluster Over-Provisioning: Proactive App Scaling
The helm chart uses the following configuration to overscale the cluster. 1 replica of placeholder-pod per node (with 2 core CPU and 2 Gi of memory request). For example, if the Kubernetes cluster is running with 15 nodes then 15 replicas of placeholder-pod will be there in the cluster.
What are some alternatives?
autoscaler - Autoscaling components for Kubernetes
k8s-prometheus-adapter - An implementation of the custom.metrics.k8s.io API using Prometheus
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
vcluster - vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
dotnet-pressure-api - An API that can apply memory and CPU pressure to test autoscaling rules in Kubernetes
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle