Beaconchain-explorer Helm Chart

Beaconchain-explorer
Analyzed version: 0.1.0

By skylenet

Beacon chain explorer built using golang and using a PostgreSQL database for storing and indexing data.

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 Beaconchain-explorer 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-beaconchain-explorer ethereum-helm-charts/beaconchain-explorer --version 0.1.0

Does the Beaconchain-explorer Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 11 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 workload from using the default namespace

1 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)

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

Learn how to fix the issue here

❌ Ensure each container has a configured readiness probe

1 occurrences:

  • metadata.name: release-name-beaconchain-explorer-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

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

4 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer (kind: StatefulSet)

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

Learn how to fix the issue here

❌ Ensure each container has a configured CPU request

2 occurrences:

  • metadata.name: release-name-beaconchain-explorer (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer-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

❌ Prevent deploying naked pods

1 occurrences:

  • metadata.name: release-name-beaconchain-explorer-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)

2 occurrences:

  • metadata.name: release-name-postgresql-init-scripts (kind: ConfigMap)
  • metadata.name: release-name-beaconchain-explorer (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 CPU limit

3 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer-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 has a configured memory request

2 occurrences:

  • metadata.name: release-name-beaconchain-explorer (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer-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-beaconchain-explorer-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 memory limit

3 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer (kind: StatefulSet)
  • metadata.name: release-name-beaconchain-explorer-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

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