Gardener Extensions

Project Gardener implements the automated management and operation of Kubernetes clusters as a service. Its main principle is to leverage Kubernetes concepts for all of its tasks.

Recently, most of the vendor specific logic has been developed in-tree. However, the project has grown to a size where it is very hard to extend, maintain, and test. With GEP-1 we have proposed how the architecture can be changed in a way to support external controllers that contain their very own vendor specifics. This way, we can keep Gardener core clean and independent.

This repository contains utilities functions and common libraries meant to ease writing the actual extension controllers.

⚠️ In order to gain synergies from commonly developed packages we are maintaining all extensions in this repository for a short period of time. Once these libraries have matured we will move out the extension controllers into their own dedicated repositories, e.g. https://github.com/gardener/gardener-extension-os-coreos.

Feedback and Support

Feedback and contributions are always welcome. Please report bugs or suggestions 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:

• Our landing page gardener.cloud
• "Gardener, the Kubernetes Botanist" blog on kubernetes.io
• GEP-1 (Gardener Enhancement Proposal) on extensibility