Deploys and manages a CloudNativePG cluster and its associated resources.
Helm Chart to install the trivy-operator PolicyReport adapter
Crowdsec helm chart is an open-source, lightweight agent to detect and respond to bad behaviours.
A Helm chart for prometheus node-exporter
A Helm chart for prometheus postgres-exporter
A Helm chart for running Fairwinds Goldilocks. See https://github.com/FairwindsOps/goldilocks
A Helm chart for Aerospike Kubernetes Operator
The data orchestration platform built for productivity.
The defectdojo persistence provider persists secureCodeBox scan results into defectdojo.
This Helm chart provides a highly available Redis implementation with a master/slave configuration and uses Sentinel sidecars for failover management
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
A Helm chart for k8s prometheus adapter
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 or 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.