Post by Project Sveltos

Managing Kubernetes add-ons at scale means answering one question repeatedly: 𝗵𝗼𝘄 𝗱𝗼 𝗜 𝗱𝗲𝗽𝗹𝗼𝘆 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝘁𝗵𝗶𝗻𝗴 𝘁𝗼 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗰𝗹𝘂𝘀𝘁𝗲𝗿, 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁𝗹𝘆? Sveltos answers it with a single Kubernetes-native resource: 𝗖𝗹𝘂𝘀𝘁𝗲𝗿𝗣𝗿𝗼𝗳𝗶𝗹𝗲. A ClusterProfile defines 𝘄𝗵𝗮𝘁 to deploy (Helm charts, Kustomize overlays, raw manifests) and 𝘄𝗵𝗲𝗿𝗲 to deploy it — using standard Kubernetes label selectors to target clusters. A single manifest deploys Kyverno to every cluster labelled 𝘦𝘯𝘷: 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘪𝘰𝘯 whether that's 1 cluster or 100. - Add a new cluster with the right label: Sveltos picks it up automatically and brings it into compliance. - Remove the label: the add-on is cleanly removed. The management cluster holds the desired state. Managed clusters hold the running state. Sveltos keeps them aligned. 𝗞𝗲𝘆 𝗽𝗿𝗼𝗽𝗲𝗿𝘁𝗶𝗲𝘀: - Declarative and GitOps-friendly - Works with any CNCF-conformant cluster (EKS, GKE, RKE2, on-prem, vCluster…) - Single point of control, no per-cluster tooling required - Cluster selection via `matchLabels` or `matchExpressions` This is the foundation everything else in Sveltos builds on. #Kubernetes #MultiCluster #GitOps #PlatformEngineering #CloudNative