2 minute read
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 extension implements Gardener’s extension contract for the OpenShift provider.
It includes OpenShift-specific controllers for
Unlike other provider extensions, it does not include controllers for
Worker resources, as well as provider-specific control plane webhooks.
Since OpenShift Virtualization is based on KubeVirt, use Gardener extension for KubeVirt provider with an OpenShift cluster.
An example for a
ControllerRegistration resource that can be used to register the controllers of this extension with Gardener can be found here.
Please find more information regarding the extensibility concepts and a detailed proposal here.
Supported Kubernetes versions
This extension supports the following Kubernetes versions:
|Kubernetes 1.19||not tested|
|Kubernetes 1.16||not tested|
|Kubernetes 1.15||not tested|
Please take a look here to see which versions are supported by Gardener in general.
How to start using or developing this extension locally
You can run the extension locally on your machine by executing
Feedback and Support
Please find further resources about out project here:
- Our landing page gardener.cloud
- “Gardener, the Kubernetes Botanist” blog on kubernetes.io
- “Gardener Project Update” blog on kubernetes.io
- GEP-1 (Gardener Enhancement Proposal) on extensibility
- GEP-4 (New
- Extensibility API documentation
- Gardener Extensions Golang library
- Gardener API Reference
Was this page helpful?