Kubernetes API server extension and controller manager managing the full lifecycle of conformant Kubernetes clusters (Shoots) as a service on AWS, Azure, GCP, and OpenStack.
Clone or download
rfranzke Merge pull request #463 from mliepold/master
Fixed an issue with project quota check
Latest commit 7517ccc Oct 17, 2018
Failed to load latest commit information.
.ci Correct way for fetching golint Oct 14, 2018
.github Update pull_request_template.md Oct 5, 2018
charts Merge pull request #464 from timuthy/fix/restrict-metadata-service Oct 17, 2018
cmd External admission controller does not react on PVs marked for deletion Oct 4, 2018
docs Correct way for fetching golint Oct 14, 2018
example Merge pull request #399 from amshuman-kr/feature/hpa-config Oct 16, 2018
hack Make HPA flags to kube-controller-manager configurable in the Shoot s… Oct 15, 2018
logo Initial version of gardener Jan 17, 2018
pkg Smooth kubelet update via docker image preload Oct 17, 2018
plugin/pkg Fixed an issue with project quota check Oct 17, 2018
vagrant Enable Ignition, shoot deletion Feb 26, 2018
vendor Force delete blocking APIServices and CRDs Sep 26, 2018
.dockerignore use docker multi stage builds Jul 31, 2018
.gitignore gitignore for virtualgo and fuse_fs Apr 10, 2018
CODEOWNERS Use @gardener/gardener-maintainers team for CODEOWNERS Oct 3, 2018
CONTRIBUTING.md Initial version of gardener Jan 17, 2018
Dockerfile Alpine 3.8 Sep 28, 2018
Gopkg.lock Force delete blocking APIServices and CRDs Sep 26, 2018
Gopkg.toml Force delete blocking APIServices and CRDs Sep 26, 2018
LICENSE.md enhance flow implementation Sep 13, 2018
Makefile Fix reset shoots method by adding reset-retry Sep 25, 2018
NOTICE.md Replace Heapster with Kubernetes metrics-server Sep 3, 2018
README.md Update README.md Aug 23, 2018
VERSION Prepare next dev cycle 0.13.0-dev Sep 28, 2018



Gardener Logo

Go Report Card CII Best Practices

The Gardener implements the automated management and operation of Kubernetes clusters as a service and aims to support that service on multiple Cloud providers (AWS, GCP, Azure, OpenStack). Its main principle is to use Kubernetes itself as base for its tasks.

In essence, the Gardener is an extension API server along with a bundle of Kubernetes controllers which introduces new API objects in an existing Kubernetes cluster (which is called Garden cluster) in order to use them for the management of further Kubernetes clusters (which are called Shoot clusters). To do that reliably and to offer a certain quality of service, it 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).

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

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

Take a look at our Gardener Helm Chart for deploying Gardener to an existing Kubernetes cluster, or at our landscape setup template to bootstrap your own Gardener system (including pre-installed configuration and Gardener Dashboard).

Feedback and Support

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 (Invite yourself to the Kubernetes Slack workspace here).