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.
Conformance test results of latest stable Gardener release, transparently visible at the CNCF testgrid:
| Provider/K8s | v1.14 | v1.13 | v1.12 | v1.11 | v1.10 | | ———– | ———– |———– |———– |———– |———– | | GCP | | | | | | | AWS | | | | | | | OpenStack | | | | | | | Azure | | | | | | | Alicloud | | | N/A | N/A | N/A | Packet1 | | | | |
1 to be determined (PR #916)
Besides the conformance tests, many more e2e tests are executed on a daily basis. Access to results of these additional e2e tests, will be provided in the near future.
See our documentation in the
/docs repository, please find the index here.
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
Feedback and contributions are always welcome!
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).
Please find further resources about out project here: