2.3 KiB
Gardener Fleet agent management
Introduction
Gardener comes with an extension that enables shoot owners to register their cluster in Fleet.
Extension Installation
The shoot-fleet-agent extension can be deployed and configured via Gardener's native resource ControllerRegistration.
Prerequisites
To let the shoot-fleet-agent operate properly, you need to have:
- a working cluster with Fleet multicluster setup enabled
- have kubeconfig with read/write access to cluster.fleet.cattle.io and secret resrouces in some namespace
ControllerRegistration
An example of a ControllerRegistration for the shoot-fleet-agent can be found here: https://github.com/ysoftdevs/gardener-extension-shoot-fleet-agent/blob/master/example/controller-registration.yaml
Configuration
The ControllerRegistration contains a Helm chart which eventually deploy the shoot-fleet-agent to seed clusters.
apiVersion: core.gardener.cloud/v1beta1
kind: ControllerRegistration
...
values:
defaultConfig:
kubeconfig: abcd
labels:
If the shoot-fleet-agent should be enabled for every shoot cluster in your Gardener managed environment, you need to globally enable it in the ControllerRegistration:
apiVersion: core.gardener.cloud/v1beta1
kind: ControllerRegistration
...
resources:
- globallyEnabled: true
kind: Extension
type: shoot-fleet-agent
Alternatively, you're given the option to only enable the service for certain shoots:
kind: Shoot
apiVersion: core.gardener.cloud/v1beta1
...
spec:
extensions:
- type: shoot-fleet-agent
...