Aws-multi-ecr-credentials Helm Chart

Aws-multi-ecr-credentials
Analyzed version: 1.4.3

By Sandora

This Chart seemlessly integrates Kubernetes with Multi AWS ECR

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 Aws-multi-ecr-credentials Helm Chart

Add Chart Repository to Helm

helm repo add aws-multi-ecr-credentials https://laviua.github.io/aws-multi-ecr-credentials/

Install Chart

helm install my-aws-multi-ecr-credentials aws-multi-ecr-credentials/aws-multi-ecr-credentials --version 1.4.3

Does the Aws-multi-ecr-credentials Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 10 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.

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

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

💡 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 CronJob scheduler is valid

1 occurrences:

  • metadata.name: release-name-cron (kind: CronJob)

💡 Incorrect value for key `schedule` - the (cron) schedule expressions is not valid and, therefore, will not work as expected

Learn how to fix the issue here

❌ Ensure CronJob has a configured deadline

1 occurrences:

  • metadata.name: release-name-cron (kind: CronJob)

💡 Missing property object `startingDeadlineSeconds` - set a time limit to the cron execution to allow killing it if exceeded

Learn how to fix the issue here

❌ Ensure each container has a configured memory limit

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

💡 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 memory request

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

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

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

💡 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 CronJob from executing jobs concurrently

1 occurrences:

  • metadata.name: release-name-cron (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

❌ Ensure each container has a configured CPU request

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

💡 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 CPU limit

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

💡 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

2 occurrences:

  • metadata.name: release-name-job (kind: Job)
  • metadata.name: release-name-cron (kind: CronJob)

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

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