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 controller implements Gardener's extension contract for the shoot-kubecost extension.
Please find more information regarding the extensibility concepts and a detailed proposal here.
Download the controller-registration.yaml from the GitHub releases. Install this manifest in the Garden cluster to enable the controller.
To configure the extension for a Shoot, add this to the manifest:
extensions:
- ...
- type: shoot-kubecost
providerConfig:
apiVersion: kubecost.extensions.config.gardener.cloud/v1alpha1
kind: Configuration
apiToken: xxxxxxxxxxxxxxxxxxxxConfiguring the apiToken is required.
Please find further resources about out project here: