2 minute read  

Gardener Extension for KubeVirt provider

CI Build status Go Report Card

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 KubeVirt provider. It includes KubeVirt-specific controllers for Infrastructure, ControlPlane, and Worker resources, as well as KubeVirt-specific control plane webhooks. Unlike other provider extensions, it does not include controllers for BackupBucket and BackupEntry resources, since KubeVirt as technology is not concerned with backup storage. Use the Gardener extension for your respective cloud provider to backup and restore your ETCD data. On OpenShift clusters, use Gardener extension for OpenShift provider.

For more information about Gardener integration with KubeVirt see this gardener.cloud blog post.

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:

VersionSupportConformance test results
Kubernetes 1.19not testedN/A
Kubernetes 1.181.18.0+N/A
Kubernetes 1.171.17.0+N/A
Kubernetes 1.16not testedN/A
Kubernetes 1.15not testedN/A

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 make start.

Static code checks and tests can be executed by running make verify. We are using Go modules for Golang package dependency management and Ginkgo/Gomega for testing.

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:


Dev Setup

Local Setup Admission

Usage As End User

Usage As Operator