5.9k
Quick Start
DatreeHelm Chart DB
Appsemble by Appsemble

Appsemble Helm Chart

Appsemble
Analyzed version: 0.20.5

By Appsemble

The open source low-code app building platform

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

Add Chart Repository to Helm

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

Install Chart

helm install my-appsemble appsemble/appsemble --version 0.20.5

Does the Appsemble chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 12 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 readiness probe

7 occurrences:

  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)
  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (kind: Pod)
  • metadata.name: release-name-appsemble-cleanup (kind: Job)
  • metadata.name: release-name-appsemble-migrate (kind: Job)
  • metadata.name: release-name-appsemble-restore (kind: Job)

💡 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

8 occurrences:

  • metadata.name: release-name-appsemble (kind: Deployment)
  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)
  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (kind: Pod)
  • metadata.name: release-name-appsemble-cleanup (kind: Job)
  • metadata.name: release-name-appsemble-migrate (kind: Job)
  • metadata.name: release-name-appsemble-restore (kind: Job)

💡 Missing property object `requests.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

1 occurrences:

  • metadata.name: appsemble-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 liveness probe

7 occurrences:

  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)
  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (kind: Pod)
  • metadata.name: release-name-appsemble-cleanup (kind: Job)
  • metadata.name: release-name-appsemble-migrate (kind: Job)
  • metadata.name: release-name-appsemble-restore (kind: Job)

💡 Missing property object `livenessProbe` - add a properly configured livenessProbe to catch possible deadlocks

Learn how to fix the issue here

❌ Prevent deploying naked pods

2 occurrences:

  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (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 Ingress from forwarding all traffic to a single container

1 occurrences:

  • metadata.name: release-name-appsemble (kind: Ingress)

💡 Incorrect value for key `host` - specify host instead of using a wildcard character ("*")

Learn how to fix the issue here

❌ Ensure each container image has a pinned (tag) version

2 occurrences:

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

❌ Ensure each container has a configured memory limit

9 occurrences:

  • metadata.name: release-name-appsemble (kind: Deployment)
  • metadata.name: appsemble-postgresql (kind: StatefulSet)
  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)
  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (kind: Pod)
  • metadata.name: release-name-appsemble-cleanup (kind: Job)
  • metadata.name: release-name-appsemble-migrate (kind: Job)
  • metadata.name: release-name-appsemble-restore (kind: Job)

💡 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

9 occurrences:

  • metadata.name: release-name-appsemble (kind: Deployment)
  • metadata.name: appsemble-postgresql (kind: StatefulSet)
  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)
  • metadata.name: release-name-appsemble-test-connection (kind: Pod)
  • metadata.name: release-name-appsemble-test-ingress (kind: Pod)
  • metadata.name: release-name-appsemble-cleanup (kind: Job)
  • metadata.name: release-name-appsemble-migrate (kind: Job)
  • metadata.name: release-name-appsemble-restore (kind: Job)

💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Prevent CronJob from executing jobs concurrently

2 occurrences:

  • metadata.name: release-name-appsemble-cleanup-resources (kind: CronJob)
  • metadata.name: release-name-appsemble-run-cronjobs (kind: CronJob)

💡 Missing property object `concurrencyPolicy` - the behavior will be more deterministic if jobs won't run concurrently

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

AppsCode Inc.

Kubeform-provider-azurerm-databox-crds

AppsCode Inc.
Delivery Hero

Prometheus-new-relic-app-exporter

Delivery Hero
AppsCode Inc.

Kubeform-provider-aws-ssm-crds

AppsCode Inc.
cankush625

Myweb - Cankush625

cankush625
[riftbit]

Loki-stack

[riftbit]
AppsCode Inc.

Kubeform-provider-google-apigee-crds

AppsCode Inc.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started

See GitHub Project
See Docs