- Home
- Kubernetes Management Platforms
- Gardener
Gardener
What it is
Gardener is an open-source service for automating Kubernetes cluster management and operation. You run a Gardener installation on your infrastructure, hosted by an existing Kubernetes cluster, and use it to deliver managed clusters at scale. It provisions consistent configurations across providers including OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud. Lifecycle actions can be started through a button or kubectl apply, with self-healing and autoscaling. Operators can apply fleet guardrails and control Kubernetes and operating-system versions and their lifecycles. Extensions add provider-specific controllers without placing that knowledge in the core. Gardener mandates the DISA Kubernetes STIG and includes a compliance checker, while noting that some requirements may be adjusted or skipped. Regional restrictions are configurable by users. The project is free and neutrally governed under NeoNephos Foundation.
For and against
For
- Open-source and free to use
- Provisions consistent clusters across providers
- Supports self-healing and autoscaling
- Provides fleet guardrails and version controls
- Includes policy and upgrade management
Against
- Requires an existing Kubernetes cluster for runtime components
- Regional compliance settings are the user's responsibility
- Some DISA requirements may be adjusted or skipped
- Documented node maximum can be temporarily exceeded
The verdict
Gardener provides provider-neutral Kubernetes fleet management with lifecycle automation, policies, and extensions. Its self-hosted requirement and configuration responsibilities matter when planning deployment.
Who it suits
It suits teams operating Kubernetes fleets across multiple infrastructure providers. Operators should be prepared to host and configure their own Gardener installation.
On the record
- Cluster portability
- It provisions clusters with identical configuration and options across different infrastructure providers.gardener.cloud · read 4 Oct 2026
- Configurable limits
- Operators can configure shoot cluster limits through CloudProfile resources, and configured limits are enforced for shoots using that profile.gardener.cloud · read 4 Oct 2026
- Deployment model
- Gardener delivers fully managed clusters at scale through your own Gardener installation.gardener.cloud · read 3 Oct 2026
- Deployment requirement
- A Gardener installation requires an existing Kubernetes cluster to host its runtime components.gardener.cloud · read 4 Oct 2026
- Extensibility
- Gardener's extension architecture supports external controllers for vendor-specific functionality.gardener.cloud · read 3 Oct 2026
- Extension architecture
- Gardener uses Kubernetes controller extensions to add infrastructure support and cluster capabilities while keeping provider-specific knowledge out of its core.gardener.cloud · read 4 Oct 2026
- Fleet controls
- Operators can control the Kubernetes and operating system versions available to clusters and manage their lifecycle.gardener.cloud · read 4 Oct 2026
- Governance
- The site says Gardener is built in the open and neutrally governed under the NeoNephos Foundation.gardener.cloud · read 4 Oct 2026
- Infrastructure
- The homepage lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud.gardener.cloud · read 3 Oct 2026
- Infrastructure integrations
- The landing page lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud.gardener.cloud · read 4 Oct 2026
- Lifecycle
- Gardener supports cluster lifecycle management, self-healing, and autoscaling across the stack.gardener.cloud · read 4 Oct 2026
- Lifecycle management
- The homepage says cluster lifecycle can be managed through a button or kubectl apply, with self-healing and auto-scaling capabilities.gardener.cloud · read 3 Oct 2026
- Limit behavior
- The documented maximum node count is not a hard runtime limit and can be temporarily exceeded during worker pool updates or changes.gardener.cloud · read 4 Oct 2026
- Purpose
- Gardener is a managed Kubernetes service framework for delivering fully managed clusters at scale through your own Gardener installation.gardener.cloud · read 4 Oct 2026
- Regional controls
- Gardener supports regional placement restrictions, but users are responsible for configuring them to meet applicable regional requirements.gardener.cloud · read 3 Oct 2026
- Scale
- The site says Gardener can run thousands of clusters while maintaining performance, resilience, and cost efficiency.gardener.cloud · read 4 Oct 2026
- Security
- Gardener mandates the DISA Security Technical Implementation Guide for Kubernetes and provides adopters a compliance checker for demonstrating DISA Kubernetes STIG compliance.gardener.cloud · read 3 Oct 2026
- 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.gardener.cloud · read 4 Oct 2026
