Kubernetes Cluster Add-ons Configured From a Single Shared Kapitan Inventory
Before running its first application, a Kubernetes cluster typically needs a common set of add-on components installed. This project keeps the configuration for these components in one Kapitan inventory, where each shared value is defined only once. A platform-baseline check script deploys the setup to a fresh kind cluster on every change and once a week. Components such as cert-manager, Kyverno, Prometheus Operator, Grafana Operator, External Secrets, Velero and Argo CD are rendered from pinned, verified recipes sourced from the kadet-hub registry. Each recipe's digest and signed attestations are checked before the inventory is compiled.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in