Node Helm Chart

Node
Analyzed version: 17.1.0

By Bitnami

Node.js is a runtime environment built on V8 JavaScript engine. Its event-driven, non-blocking I/O model enables the development of fast, scalable, and data-intensive server applications.

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

Add Chart Repository to Helm

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

Install Chart

helm install my-node bitnami/node --version 17.1.0

Does the Node chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 7 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 CPU limit

2 occurrences:

  • metadata.name: release-name-mongodb (kind: Deployment)
  • metadata.name: release-name-node (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

❌ Prevent workload from using the default namespace

2 occurrences:

  • metadata.name: release-name-mongodb (kind: Deployment)
  • metadata.name: release-name-node (kind: Deployment)

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

Learn how to fix the issue here

❌ Prevent container security vulnerability (CVE-2021-25741)

2 occurrences:

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

💡 Forbidden property object `subPath` - malicious users can gain access to files & directories outside of the volume

Learn how to fix the issue here

❌ Prevent ConfigMap security vulnerability (CVE-2021-25742)

1 occurrences:

  • metadata.name: release-name-mongodb-common-scripts (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

2 occurrences:

  • metadata.name: release-name-mongodb (kind: Deployment)
  • metadata.name: release-name-node (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

2 occurrences:

  • metadata.name: release-name-mongodb (kind: Deployment)
  • metadata.name: release-name-node (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

2 occurrences:

  • metadata.name: release-name-mongodb (kind: Deployment)
  • metadata.name: release-name-node (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

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