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 operates on the Infrastructure
resource in the extensions.gardener.cloud/v1alpha1
API group. It manages those objects that are requesting an Packet infrastructure (.spec.type=packet
):
---
apiVersion: extensions.gardener.cloud/v1alpha1
kind: Infrastructure
metadata:
name: infrastructure
spec:
type: packet
region: ewr1
secretRef:
name: cloudprovider
namespace: shoot--foobar--packet
providerConfig:
apiVersion: packet.provider.extensions.gardener.cloud/v1alpha1
kind: InfrastructureConfig
sshPublicKey: ...
Please find a concrete example in the example
folder.
After reconciliation the resulting data will be stored in the resource's .status
field:
...
status:
...
providerStatus:
apiVersion: packet.provider.extensions.gardener.cloud/v1alpha1
kind: InfrastructureStatus
...
An example for a ControllerRegistration
resource that can be used to register this controller to Gardener can be found here.
Please find more information regarding the extensibility concepts and a detailed proposal here.
How to start using or developing this extension controller locally
You can run the controller locally on your machine by executing make start-provider-packet
.
Static code checks and tests can be executed by running VERIFY=true make all
. We are using dep 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: