5.9k
Quick Start
DatreeHelm Chart DB
Centralbrain by ScienceMesh

Centralbrain Helm Chart

Centralbrain
Analyzed version: 0.0.3

By ScienceMesh

Central Brain is the obserbavility component for the IOP

How to install the chart
Does the chart contain security gaps?
How to install the chart
Does the chart contain security gaps?

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.

How to install the chart
Does the chart follow industry best practices
Latest version: 15.5.3
View GitHub

How to Install the Centralbrain Helm Chart

Add Chart Repository to Helm

helm repo add sciencemesh https://sciencemesh.github.io/charts/

Install Chart

helm install my-centralbrain sciencemesh/centralbrain --version 0.0.3

Does the Centralbrain chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 11 misconfigurations.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Prevent deprecated APIs in Kubernetes v1.17

2 occurrences:

  • metadata.name: release-name-kube-state-metrics (kind: ClusterRole)
  • metadata.name: release-name-kube-state-metrics (kind: ClusterRoleBinding)

💡 Incorrect value for key `apiVersion` - the version you are trying to use is not supported by the Kubernetes cluster version (>=1.17)

Learn how to fix the issue here

❌ Ensure each container has a configured liveness probe

3 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (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 CPU request

6 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-grafana (kind: Deployment)
  • metadata.name: release-name-kube-state-metrics (kind: Deployment)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (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

6 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-grafana (kind: Deployment)
  • metadata.name: release-name-kube-state-metrics (kind: Deployment)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (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

❌ Prevent workload from using the default namespace

5 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-grafana (kind: Deployment)
  • metadata.name: release-name-kube-state-metrics (kind: Deployment)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (kind: Pod)

💡 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)

6 occurrences:

  • metadata.name: release-name-grafana (kind: Deployment)
  • metadata.name: release-name-prometheus-server (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

❌ Ensure each container has a configured CPU limit

6 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-grafana (kind: Deployment)
  • metadata.name: release-name-kube-state-metrics (kind: Deployment)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (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 readiness probe

3 occurrences:

  • metadata.name: release-name-prometheus-node-exporter (kind: DaemonSet)
  • metadata.name: release-name-prometheus-server (kind: Deployment)
  • metadata.name: release-name-grafana-test (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 deploying naked pods

1 occurrences:

  • metadata.name: release-name-grafana-test (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)

3 occurrences:

  • metadata.name: release-name-grafana (kind: ConfigMap)
  • metadata.name: release-name-grafana-test (kind: ConfigMap)
  • metadata.name: release-name-prometheus-server (kind: ConfigMap)

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

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.

Related Charts

Avesha

Kubeslice-controller

Avesha
[riftbit]

Grafana-tempo

[riftbit]
Rasa

Duckling

Rasa
Bitnami

Keycloak

Bitnami
rcreate

Opentsdb

rcreate
TrueCharts

Adminer

TrueCharts

Reveal misconfigurations within minutes

3 Quick Steps to Get Started

See GitHub Project
See Docs