Skip to content
Kubernetes API server extension and controller managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, and OpenStack with minimal TCO.
Branch: master
Clone or download
Latest commit 2831078 May 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.ci Major alerts refactoring Mar 27, 2019
.github Add issue templates Apr 26, 2019
.test-defs updated golang image for testdefs May 7, 2019
charts Merge pull request #1018 from gardener/feature/calico-3.7.2 May 20, 2019
cmd Delete dirty soft link Apr 10, 2019
docs Prevent volume usage alerts May 16, 2019
example Merge pull request #952 from rfranzke/feature/node-template May 14, 2019
hack Merge pull request #952 from rfranzke/feature/node-template May 14, 2019
logo Initial version of gardener Jan 17, 2018
pkg Merge pull request #1018 from gardener/feature/calico-3.7.2 May 20, 2019
plugin/pkg Make SeedManager Admission Plugin configurable to support different s… Apr 11, 2019
test Fix / Enhance / Refactor cleanup Apr 25, 2019
vagrant Enable Ignition, shoot deletion Feb 26, 2018
vendor Fix / Enhance / Refactor cleanup Apr 25, 2019
.dockerignore Some enhancement as per code review Jan 24, 2019
.gitignore add integration tests framework Jan 25, 2019 Add list of Gardener adopters Apr 10, 2019
CODEOWNERS Use @gardener/gardener-maintainers team for CODEOWNERS Oct 3, 2018 Initial version of gardener Jan 17, 2018
Dockerfile Clean up cluster-service label May 8, 2019
Gopkg.lock Fix / Enhance / Refactor cleanup Apr 25, 2019
Gopkg.toml Resolve dependencies of Alicloud OSS SDK Apr 16, 2019 Some enhancement as per code review Jan 24, 2019
Makefile Add script easing local installation of extensions Feb 13, 2019 Remove monocular addon Jan 16, 2019 slack channel badge, virtual installer May 10, 2019
VERSION Prepare next dev cycle 0.23.0-dev May 16, 2019


Gardener Logo

Slack channel #gardener Go Report Card CII Best Practices

Gardener implements the automated management and operation of Kubernetes clusters as a service and provides support for multiple cloud providers (Alicloud, AWS, Azure, GCP, OpenStack, ...). Its main principle is to leverage Kubernetes concepts for all of its tasks.

In essence, Gardener is an extension API server that comes along with a bundle of custom controllers. It introduces new API objects in an existing Kubernetes cluster (which is called garden cluster) in order to use them for the management of end-user Kubernetes clusters (which are called shoot clusters). These shoot clusters are described via declarative cluster specifications which are observed by the controllers. They will bring up the clusters, reconcile their state, perform automated updates and make sure they are always up and running.

To accomplish these tasks reliably and to offer a certain quality of service, Gardener requires to control the main components of a Kubernetes cluster (etcd, API server, controller manager, scheduler). These so-called control plane components are hosted in Kubernetes clusters themselves (which are called seed clusters). This is the main difference compared to many other OSS cluster provisioning tools: The shoot clusters do not have dedicated master VMs, instead, the control plane is deployed as native Kubernetes workload into the seeds. This does not only effectively reducing the total costs of ownership, it also allows easier implementations for "day-2 operations" (like cluster updates or robustness) by relying on all the mature Kubernetes features and capabilities.

Please find more information regarding the concepts and a detailed description of the architecture in our Gardener Wiki and our blog post on

To start using or developing the Gardener locally

See our documentation in the /docs repository, please find the index here.

Setting up your own Gardener landscape in the cloud

The quickest way to test drive Gardener is to install it virtually onto an existing Kubernetes cluster, just like you would install any other Kubernetes-ready application. Launch your automatic installer here

We also have a Gardener Helm Chart. Alternatively you can use our garden setup project to create a fully configured Gardener landscape which also includes our Gardener Dashboard.

Feedback and Support

Feedback and contributions are always welcome!

All channels for getting in touch or learning about our project are listed under the community section. We are cordially inviting interested parties to join our weekly meetings.

Please report bugs or suggestions about our Kubernetes clusters as such or the Gardener itself as GitHub issues or join our Slack channel #gardener (please invite yourself to the Kubernetes workspace here).

Learn more!

Please find further resources about out project here:

You can’t perform that action at this time.