K8s-event-logger Helm Chart

K8s-event-logger
Analyzed version: 1.0.0

By Delivery Hero

This chart runs a pod that simply watches Kubernetes Events and logs them to stdout in JSON to be collected and stored by your logging solution, e.g. [fluentd](https://github.com/helm/charts/tree/master/stable/fluentd) or [fluent-bit](https://github.com/helm/charts/tree/master/stable/fluent-bit). https://github.com/max-rocket-internet/k8s-event-logger Events in Kubernetes log very important information. If are trying to understand what happened in the past then these events show clearly what your Kubernetes cluster was thinking and doing. Some examples: - Pod events like failed probes, crashes, scheduling related information like `TriggeredScaleUp` or `FailedScheduling` - HorizontalPodAutoscaler events like scaling up and down - Deployment events like scaling in and out of ReplicaSets - Ingress events like create and update The problem is that these events are simply API objects in Kubernetes and are only stored for about 1 hour. Without some way of storing these events, debugging a problem in the past very tricky.

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 K8s-event-logger Helm Chart

Add Chart Repository to Helm

helm repo add deliveryhero https://charts.deliveryhero.io/

Install Chart

helm install my-k8s-event-logger deliveryhero/k8s-event-logger --version 1.0.0

Does the K8s-event-logger Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 3 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 deprecated APIs in Kubernetes v1.17

1 occurrences:

  • metadata.name: release-name-k8s-event-logger (kind: ClusterRole)

💡 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

1 occurrences:

  • metadata.name: release-name-k8s-event-logger (kind: Deployment)

💡 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

1 occurrences:

  • metadata.name: release-name-k8s-event-logger (kind: Deployment)

💡 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

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