Nfs-server-provisioner Helm Chart

Nfs-server-provisioner
Analyzed version: 1.3.0

By raphael

nfs-server-provisioner is an out-of-tree dynamic provisioner for Kubernetes. You can use it to quickly & easily deploy shared storage that works almost anywhere.

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 Nfs-server-provisioner Helm Chart

Add Chart Repository to Helm

helm repo add raphael https://raphaelmonrouzeau.github.io/charts/repository/

Install Chart

helm install my-nfs-server-provisioner raphael/nfs-server-provisioner --version 1.3.0

Does the Nfs-server-provisioner Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 4 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 memory limit

1 occurrences:

  • metadata.name: release-name-nfs-server-provisioner (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-nfs-server-provisioner (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

❌ Ensure each container has a configured memory request

1 occurrences:

  • metadata.name: release-name-nfs-server-provisioner (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-nfs-server-provisioner (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

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