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-rsyslog-relp extension.
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.
Example configuration for this extension controller:
apiVersion: rsyslog-relp.extensions.config.gardener.cloud/v1alpha1
kind: RsyslogRelpConfig
target: relp-server.foo.bar
port: 1520
tls:
enabled: true
authMode: name
permittedPeer: rsyslog-server-peer
secretReferenceName: rsyslog-relep-tlsExample extension resource: