Geth Helm Chart

Geth
Analyzed version: 0.2.1

By skylenet

Go Ethereum (Geth for short) is one of the original implementations of the Ethereum protocol. Currently, it is the most widespread client with the biggest user base and variety of tooling for users and developers. It is written in Go, fully open source and licensed under the GNU LGPL v3

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

Add Chart Repository to Helm

helm repo add ethereum-helm-charts https://skylenet.github.io/ethereum-helm-charts

Install Chart

helm install my-geth ethereum-helm-charts/geth --version 0.2.1

Does the Geth Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 9 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 deploying naked pods

1 occurrences:

  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 Incorrect value for key `kind` - raw pod won't be rescheduled in the event of a node failure

Learn how to fix the issue here

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

1 occurrences:

  • metadata.name: release-name-geth (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-geth (kind: StatefulSet)
  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 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 liveness probe

1 occurrences:

  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 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-geth-test-connection (kind: Pod)

💡 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

❌ Ensure each container has a configured CPU request

2 occurrences:

  • metadata.name: release-name-geth (kind: StatefulSet)
  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 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-geth (kind: StatefulSet)
  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 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-geth (kind: StatefulSet)
  • metadata.name: release-name-geth-test-connection (kind: Pod)

💡 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 image has a pinned (tag) version

2 occurrences:

  • metadata.name: release-name-geth (kind: StatefulSet)
  • metadata.name: release-name-geth-test-connection (kind: Pod)

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

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