5.9k
Quick Start
DatreeHelm Chart DB
Nginx-service-mesh by nginx

Nginx-service-mesh Helm Chart

Nginx-service-mesh
Analyzed version: 0.4.0
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 Nginx-service-mesh Helm Chart

Add Chart Repository to Helm

helm repo add nginx https://helm.nginx.com/stable

Install Chart

helm install my-nginx-service-mesh nginx/nginx-service-mesh --version 0.4.0

Does the Nginx-service-mesh chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 8 misconfigurations.

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

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

6 occurrences:

  • metadata.name: grafana-config (kind: ConfigMap)
  • metadata.name: grafana-dashboards (kind: ConfigMap)
  • metadata.name: nats-config (kind: ConfigMap)
  • metadata.name: spire-agent (kind: ConfigMap)
  • metadata.name: spire-server (kind: ConfigMap)
  • metadata.name: k8s-workload-registrar (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

14 occurrences:

  • metadata.name: spire-agent (kind: DaemonSet)
  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: nginx-mesh-api (kind: Deployment)
  • metadata.name: nginx-mesh-metrics (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (kind: Job)

💡 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

14 occurrences:

  • metadata.name: spire-agent (kind: DaemonSet)
  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: nginx-mesh-api (kind: Deployment)
  • metadata.name: nginx-mesh-metrics (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (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

❌ Ensure each container has a configured memory limit

14 occurrences:

  • metadata.name: spire-agent (kind: DaemonSet)
  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: nginx-mesh-api (kind: Deployment)
  • metadata.name: nginx-mesh-metrics (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (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

14 occurrences:

  • metadata.name: spire-agent (kind: DaemonSet)
  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: nginx-mesh-api (kind: Deployment)
  • metadata.name: nginx-mesh-metrics (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (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

❌ Ensure each container has a configured liveness probe

9 occurrences:

  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (kind: Job)

💡 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

9 occurrences:

  • metadata.name: grafana (kind: Deployment)
  • metadata.name: jaeger (kind: Deployment)
  • metadata.name: nats-server (kind: Deployment)
  • metadata.name: prometheus (kind: Deployment)
  • metadata.name: spire-server (kind: StatefulSet)
  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (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 image has a pinned (tag) version

4 occurrences:

  • metadata.name: remove-spiffeids (kind: Job)
  • metadata.name: remove-namespace-label (kind: Job)
  • metadata.name: turn-proxies-transparent (kind: Job)
  • metadata.name: label-namespace (kind: Job)

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

Related Charts

AppsCode Inc.

Kubeform-provider-azurerm-kubernetescluster-crds

AppsCode Inc.
AppsCode Inc.

Kubeform-provider-upcloud

AppsCode Inc.
AppsCode Inc.

Prepare-kubernetes-cluster

AppsCode Inc.
startxfr

Example-deployment

startxfr
k8s@home

Teedy

k8s@home
NTP Pool Project

Locationcode

NTP Pool Project

Reveal misconfigurations within minutes

3 Quick Steps to Get Started

See GitHub Project
See Docs