Cluster-overprovisioner Helm Chart

Cluster-overprovisioner
Analyzed version: 0.7.8

By Delivery Hero

This chart provide a buffer for cluster autoscaling to allow overprovisioning of cluster nodes. This is desired when you have work loads that need to scale up quickly without waiting for the new cluster nodes to be created and join the cluster. It works by creating a deployment that creates pods of a lower than default `PriorityClass`. These pods request resources from the cluster but don't actually consume any resources. These pods are then evicted allowing other normal pods to be created while also triggering a scale-up by the [cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler). This approach is the [current recommended method to achieve overprovisioning](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-can-i-configure-overprovisioning-with-cluster-autoscaler).

Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.

Latest version: 15.5.3
View GitHub

How to Install the Cluster-overprovisioner Helm Chart

Add Chart Repository to Helm

helm repo add deliveryhero https://charts.deliveryhero.io/

Install Chart

helm install my-cluster-overprovisioner deliveryhero/cluster-overprovisioner --version 0.7.8

Does the Cluster-overprovisioner Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 3 of the best practices recommended by the industry.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Prevent workload from using the default namespace

1 occurrences:

  • metadata.name: release-name-cluster-overprovisioner-default (kind: Deployment)

💡 Incorrect value for key `namespace` - use an explicit namespace instead of the default one (`default`)

Learn how to fix the issue here

❌ Ensure each container has a configured liveness probe

1 occurrences:

  • metadata.name: release-name-cluster-overprovisioner-default (kind: Deployment)

💡 Missing property object `livenessProbe` - add a properly configured livenessProbe to catch possible deadlocks

Learn how to fix the issue here

❌ Ensure each container has a configured readiness probe

1 occurrences:

  • metadata.name: release-name-cluster-overprovisioner-default (kind: Deployment)

💡 Missing property object `readinessProbe` - add a properly configured readinessProbe to notify kubelet your Pods are ready for traffic

Learn how to fix the issue here

This is some text inside of a div block.
This is some text inside of a div block.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started