Geode Helm Chart

Geode
Analyzed version: 0.4.19

By Bitnami

Apache Geode is a data management platform that provides advanced capabilities for data-intensive 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 Geode Helm Chart

Add Chart Repository to Helm

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

Install Chart

helm install my-geode bitnami/geode --version 0.4.19

Does the Geode chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 5 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 memory request

2 occurrences:

  • metadata.name: release-name-geode-locator (kind: StatefulSet)
  • metadata.name: release-name-geode-server (kind: StatefulSet)

💡 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-geode-locator (kind: StatefulSet)
  • metadata.name: release-name-geode-server (kind: StatefulSet)

💡 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-geode-locator (kind: StatefulSet)
  • metadata.name: release-name-geode-server (kind: StatefulSet)

💡 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

2 occurrences:

  • metadata.name: release-name-geode-locator (kind: StatefulSet)
  • metadata.name: release-name-geode-server (kind: StatefulSet)

💡 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-geode-locator (kind: StatefulSet)
  • metadata.name: release-name-geode-server (kind: StatefulSet)

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

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