5.9k
Quick Start
DatreeHelm Chart DB
Vertical-pod-autoscaler by [riftbit]

Vertical-pod-autoscaler Helm Chart

Vertical-pod-autoscaler
Analyzed version: 3.6.1

By [riftbit]

Set of components that automatically adjust the amount of CPU and memory requested by pods running in the Kubernetes Cluster

How to install the chart
Does the chart contain security gaps?
How to install the chart
Does the chart contain security gaps?

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.

How to install the chart
Does the chart follow industry best practices
Latest version: 15.5.3
View GitHub

How to Install the Vertical-pod-autoscaler Helm Chart

Add Chart Repository to Helm

helm repo add riftbit https://charts.riftbit.com/

Install Chart

helm install my-vertical-pod-autoscaler riftbit/vertical-pod-autoscaler --version 3.6.1

Does the Vertical-pod-autoscaler chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 8 misconfigurations.

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

❌ Ensure each container has a configured liveness probe

4 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 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

4 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 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

❌ Prevent deploying naked pods

4 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Incorrect value for key `kind` - raw pod won't be rescheduled in the event of a node failure

Learn how to fix the issue here

❌ Ensure each container has a configured memory request

7 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-updater (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Missing property object `requests.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU request

7 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-updater (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Missing property object `requests.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured memory limit

7 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-updater (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Missing property object `limits.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU limit

7 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-updater (kind: Deployment)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container image has a pinned (tag) version

4 occurrences:

  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-metri-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-admission-controller-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-recommender-metrics-test-connection (kind: Pod)
  • metadata.name: release-name-vertical-pod-autoscaler-updater-metrics-test-connection (kind: Pod)

💡 Incorrect value for key `image` - specify an image version to avoid unpleasant "version surprises" in the future

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.

Related Charts

sergk

Cd-pipeline-operator

sergk
TrueCharts

Openhab

TrueCharts
criscola

Kubernetes-dbaas

criscola
TrueCharts

Apache-musicindex

TrueCharts
Lifen

Op-scim-bridge

Lifen
k8s@home

Minio-console

k8s@home

Reveal misconfigurations within minutes

3 Quick Steps to Get Started

See GitHub Project
See Docs