ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Rancher Fleet's hub-and-spoke GitOps model lets platform teams sync apps across many clusters using label selectors. Here is a concrete rollout pattern, verification steps, and the limits to plan around.
Managing Kubernetes scale with Gardener Shoot Clusters: The multi‑cluster management bottleneck occurs when scaling to dozens of clusters across cloud providers. Gardener turns cluster lifecycle into a declarative object, simplifying provisioning and scaling.
Stop duplicating Argo CD Application manifests. Learn how to use ApplicationSets and generators to automate multi-cluster deployments from a single template.
Learn how Gardener uses Seed clusters to isolate Kubernetes control planes, reducing the blast radius of failures and enabling multi-cloud management.
Learn how to use the Rancher agent to import existing Kubernetes clusters into a centralized management plane, reducing configuration drift and simplifying multi-cluster RBAC.
Declare DNS, monitoring, or logging once per seed as a Gardener Addon and let the controller keep them in sync across all shoots, reducing manual toil and drift.
Rancher's multi-cluster management centralizes auth, RBAC, and GitOps delivery across imported and provisioned clusters — but the management plane itself becomes a dependency you must design for.
Gardener lets you hibernate a shoot cluster to cut worker VM costs, but version-sensitive fields and residual charges mean you need a verification routine before relying on it for cost governance.
Use Argo CD ApplicationSet to generate many Applications from one template driven by Git data. Covers minimal design, trust boundaries, operational checks, failure modes and when to split the design.
rancher
gardener
kubernetes
argocd