Freedom251 › Kubernetes Management Platforms
Gardener
What Gardener is
Gardener automates the management and operation of Kubernetes clusters as a service. It delivers fully managed clusters through a Gardener installation that users run, and that installation requires an existing Kubernetes cluster to host its runtime components. The project lists infrastructure including OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud, and says it provisions clusters with consistent configurations across providers. Operators can manage cluster lifecycles through a button or kubectl apply, with self-healing and autoscaling. Fleet controls support shared guardrails and control which Kubernetes and operating system versions are available and their lifecycle. Its extension architecture supports external controllers for provider-specific functionality. Gardener mandates the DISA Kubernetes Security Technical Implementation Guide and provides a compliance checker, though some requirements are adjusted or skipped when not applicable or optimal for its environment. Regional placement restrictions are supported, but users are responsible for configuring them to meet applicable requirements. The project is open source and governed under the NeoNephos Foundation.
Who it suits
Gardener suits operators who need to manage Kubernetes clusters across infrastructure providers from their own installation. Users must have an existing Kubernetes cluster to host its runtime components and configure regional placement restrictions themselves.
What it does well
- Manages cluster lifecycle with self-healing and autoscaling
- Supports multiple listed infrastructure providers
- Fleet controls provide shared guardrails
- Provides a DISA Kubernetes STIG compliance checker
What to know first
- Requires an existing Kubernetes cluster for runtime components
- Users must configure regional placement restrictions
- Some DISA requirements are adjusted or skipped
Getting started
- Visit the Gardener website.
- Prepare an existing Kubernetes cluster to host Gardener’s runtime components.
- Install and operate Gardener on that cluster.
- Use Gardener’s cluster lifecycle controls to provision and manage clusters.
Verdict
Gardener combines multi-provider cluster management with lifecycle automation and fleet controls. Its installation requirement and responsibility for regional configuration are important considerations for operators.
Questions
Is Gardener free?
Yes. Gardener is free and open source.
Which platforms does Gardener support?
Its platforms are API, self-hosted, and web.
Which infrastructure environments are supported?
Supported environments include Alibaba Cloud, AWS, Azure, Equinix Metal, GCP, Hetzner Cloud, IronCore, KubeVirt, metal-stack, OpenStack, STACKIT, and vSphere.
Does Gardener support multi-cluster management and upgrades?
Yes. It supports multi-cluster management and upgrade management.
What Kubernetes security support does Gardener provide?
It mandates the DISA Security Technical Implementation Guide for Kubernetes and provides a compliance checker. Its compliance report says some requirements are adjusted or skipped when they are not applicable or optimal for Gardener’s environment.
Who governs the Gardener project?
Gardener says it is built in the open and neutrally governed under the NeoNephos Foundation.
Facts from Gardener's own pages
- Cluster portability
- It provisions clusters with identical configuration and options across different infrastructure providers. · gardener.cloud, 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, 4 Oct 2026
- Deployment model
- Gardener delivers fully managed clusters at scale through your own Gardener installation. · gardener.cloud, 3 Oct 2026
- Deployment requirement
- A Gardener installation requires an existing Kubernetes cluster to host its runtime components. · gardener.cloud, 4 Oct 2026
- Extensibility
- Gardener's extension architecture supports external controllers for vendor-specific functionality. · gardener.cloud, 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, 4 Oct 2026
- Fleet controls
- Operators can control the Kubernetes and operating system versions available to clusters and manage their lifecycle. · gardener.cloud, 4 Oct 2026
- Governance
- The site says Gardener is built in the open and neutrally governed under the NeoNephos Foundation. · gardener.cloud, 4 Oct 2026
- Infrastructure
- The homepage lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud. · gardener.cloud, 3 Oct 2026
- Infrastructure integrations
- The landing page lists OpenStack, metal-stack, IronCore, STACKIT, AWS, Azure, Google Cloud, and Alibaba Cloud. · gardener.cloud, 4 Oct 2026
- Lifecycle
- Gardener supports cluster lifecycle management, self-healing, and autoscaling across the stack. · gardener.cloud, 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, 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, 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, 4 Oct 2026
- Regional controls
- Gardener supports regional placement restrictions, but users are responsible for configuring them to meet applicable regional requirements. · gardener.cloud, 3 Oct 2026
- Scale
- The site says Gardener can run thousands of clusters while maintaining performance, resilience, and cost efficiency. · gardener.cloud, 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, 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, 4 Oct 2026
- Security guidance
- Gardener aims to follow DISA's Kubernetes Security Technical Implementation Guide and checks security-hardened shoot cluster configurations for every release. · gardener.cloud, 4 Oct 2026
- Support
- The documentation directs users to community channels, GitHub Issues, and the Gardener community on Slack for assistance and questions. · gardener.cloud, 4 Oct 2026
- Who uses it
- The adopter page identifies SAP BTP as using Gardener to deploy and manage Kubernetes clusters uniformly across infrastructures. · gardener.cloud, 3 Oct 2026
Where Gardener stands on Freedom251
- Kubernetes Management Platforms#10 of 29