Iperf3 Helm Chart

Iperf3
Analyzed version: 0.1.0

By cgiraldo

iPerf3 is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing, buffers and protocols (TCP, UDP, SCTP with IPv4 and IPv6). For each test it reports the bandwidth, loss, and other parameters.

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 Iperf3 Helm Chart

Add Chart Repository to Helm

helm repo add gradiant-openverso https://gradiant.github.io/openverso-charts/

Install Chart

helm install my-iperf3 gradiant-openverso/iperf3 --version 0.1.0

Does the Iperf3 Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 8 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.

❌ Ensure each container has a configured liveness probe

1 occurrences:

  • metadata.name: release-name-iperf3 (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-iperf3 (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

❌ Prevent workload from using the default namespace

1 occurrences:

  • metadata.name: release-name-iperf3 (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 image has a pinned (tag) version

1 occurrences:

  • metadata.name: release-name-iperf3 (kind: Deployment)

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

Learn how to fix the issue here

❌ Ensure each container has a configured memory request

1 occurrences:

  • metadata.name: release-name-iperf3 (kind: Deployment)

💡 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

1 occurrences:

  • metadata.name: release-name-iperf3 (kind: Deployment)

💡 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

1 occurrences:

  • metadata.name: release-name-iperf3 (kind: Deployment)

💡 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

1 occurrences:

  • metadata.name: release-name-iperf3 (kind: Deployment)

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

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