Menu

1 / 5

Kubernetes cluster add-ons with one set of shared values

DEV Community: kubernetes·Moep90·8 days ago
#JbiO8fGM
#devtokubernetes#devto#dev#platform#podinfo
Reading 0:00
15s threshold

Before a cluster runs its first app, a small team usually adds the same

things: certificates, an admission policy, metrics and dashboards, a way to

get secrets in, backups, and a tool that deploys from Git. Each of them is

an operator that reads custom resources. Those resources name each other.

A Certificate names a ClusterIssuer, an ExternalSecret names a

ClusterSecretStore, and a Kyverno policy selects namespaces by their

labels. Kept in separate charts and manifests, each of these names is

typed again in every file that uses it.

This post keeps those resources in one Kapitan

inventory , where each shared name is set once. The

project is

platform-baseline

in kadet-hub/examples. Its check script deploys it to a new

kind cluster on every change and once a week, and fails

when one of the steps below stops working.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.