Calico-node Helm Chart

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 Calico-node Helm Chart

Add Chart Repository to Helm

helm repo add arhatdev https://helm-charts.arhat.dev

Install Chart

helm install my-calico-node arhatdev/calico-node --version 0.1.7

Does the Calico-node Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 5 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 ConfigMap security vulnerability (CVE-2021-25742)

1 occurrences:

  • metadata.name: calico-config (kind: ConfigMap)

💡 Missing property object `allow-snippet-annotations` - set it to "false" to override default behaviour

Learn how to fix the issue here

❌ Ensure each container has a configured memory request

1 occurrences:

  • metadata.name: release-name-calico-node (kind: DaemonSet)

💡 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 memory limit

1 occurrences:

  • metadata.name: release-name-calico-node (kind: DaemonSet)

💡 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-calico-node (kind: DaemonSet)

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

Learn how to fix the issue here

❌ Prevent containers from having root access capabilities

1 occurrences:

  • metadata.name: release-name-calico-node (kind: DaemonSet)

💡 Incorrect value for key `privileged` - this mode will allow the container the same access as processes running on the host

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