Gardener
gardener.cloud
- Free plan
- Web
- API
- Self-hosted
What Gardener is
Gardener automates Kubernetes cluster management as a service through an installation that organizations run themselves. That installation requires an existing Kubernetes cluster to host its runtime components, then delivers managed clusters across infrastructure providers. Listed environments include OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, Alibaba Cloud, Equinix Metal, GCP, Hetzner Cloud, KubeVirt, and vSphere. Gardener aims to keep cluster configurations and options consistent across providers and says it can operate thousands of clusters. Lifecycle actions can be performed through a button or kubectl apply, with self-healing and autoscaling. Operators can apply shared guardrails and control supported Kubernetes and operating-system versions. Kubernetes controller extensions add provider-specific capabilities without placing that knowledge in the core. Gardener mandates the DISA Kubernetes STIG and provides a compliance checker, while noting some requirements may be adjusted or skipped. Regional restrictions are supported but must be configured by users.
Who it suits
Gardener suits platform teams operating Kubernetes across multiple infrastructures and clusters. It is relevant to operators needing lifecycle automation, fleet policies, provider extensions, and self-hosted control.
Good to know, and what to watch
- Automates cluster lifecycle management
- Supports multi-cluster policies and upgrades
- Works across many infrastructure providers
- Provides self-healing and autoscaling
- Offers Kubernetes STIG compliance checking
- Requires an existing Kubernetes cluster
- Regional compliance settings require user configuration
- Some DISA requirements may be adjusted or skipped
- Maximum node counts are not hard runtime limits
The verdict
Gardener is designed for teams managing Kubernetes fleets across varied infrastructure. Its self-hosted requirement and configuration responsibilities should be planned before deployment.
What the maker publishes
- Cluster portability
- Gardener provisions clusters with identical configuration and options across infrastructure providers. source
- Cluster portability
- It provisions clusters with identical configuration and options across different infrastructure providers. source
- Configurable limits
- Operators can configure shoot cluster limits through CloudProfile resources, and configured limits are enforced for shoots using that profile. source
- Deployment model
- Gardener delivers fully managed clusters at scale through your own Gardener installation. source
- Deployment requirement
- A Gardener installation requires an existing Kubernetes cluster to host its runtime components. source
- Extensibility
- Gardener's extension architecture supports external controllers for vendor-specific functionality. source
- Extension architecture
- Gardener uses Kubernetes controller extensions to add infrastructure support and cluster capabilities while keeping provider-specific knowledge out of its core. source
- Fleet controls
- Operators can apply shared guardrails across clusters and control available Kubernetes and operating system versions and their lifecycle. source
- Fleet controls
- Operators can control the Kubernetes and operating system versions available to clusters and manage their lifecycle. source
- Governance
- Gardener says it is built in the open and neutrally governed under the NeoNephos Foundation. source
- Governance
- The site says Gardener is built in the open and neutrally governed under the NeoNephos Foundation. source
- Infrastructure
- The homepage lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud. source
- Infrastructure integrations
- The landing page lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud. source
- Lifecycle
- Gardener supports cluster lifecycle management, self-healing, and autoscaling across the stack. source
- Lifecycle management
- The homepage says cluster lifecycle can be managed through a button or kubectl apply, with self-healing and auto-scaling capabilities. source
- Limit behavior
- The documented maximum node count is not a hard runtime limit and can be temporarily exceeded during worker pool updates or changes. source
- Purpose
- Gardener automates management and operation of Kubernetes clusters as a service. source
- Purpose
- Gardener is a managed Kubernetes service framework for delivering fully managed clusters at scale through your own Gardener installation. source
- Regional controls
- Gardener supports regional placement restrictions, but users are responsible for configuring them to meet applicable regional requirements. source
- Scale
- Gardener says it can run thousands of clusters while maintaining performance, resilience, and cost efficiency. source
- Scale
- The site says Gardener can run thousands of clusters while maintaining performance, resilience, and cost efficiency. source
- Security
- Gardener mandates the DISA Security Technical Implementation Guide for Kubernetes and provides adopters a compliance checker for demonstrating DISA Kubernetes STIG compliance. source
- Security caveat
- Gardener's compliance report says some DISA requirements are adjusted or skipped when they are not applicable or optimal for Gardener's environment. source
- Security guidance
- Gardener aims to follow DISA's Kubernetes Security Technical Implementation Guide and checks security-hardened shoot cluster configurations for every release. source
Checked against the maker's pages on 4 Oct 2026.