What needs to be implemented to support a new infrastructure provider?Īs part of the shoot flow Gardener will create a special CRD in the seed cluster that needs to be reconciled by an extension controller, for example:ĪpiVersion: /v1alpha1 kind: ControlPlane metadata: If SNI is enabled, then the Service from above is of type ClusterIP and Gardner will not create ControlPlane resources with purpose exposure. The shoot cluster's kube-apiserver are exposed via a Service of type LoadBalancer from the shoot provider (you may run the control plane of an Azure shoot in a GCP seed) it's the seed provider extension controller that should act on the ControlPlane resources with purpose exposure. Its purpose is to trigger the deployment of such provider-specific components in the shoot namespace in the seed cluster that are needed to expose the kube-apiserver. Instead, it creates a ControlPlane CRD with purpose exposure that should be picked up by provider extensions. Which control plane resources are required?Īs mentioned in the controlplane document Gardener shall not deploy any other provider-specific component. Now, Gardener commissions an external, provider-specific controller to take over this task. AWS Load Balancer Readvertiser.īefore using ControlPlane resources with purpose exposure Gardener was having different Helm charts for the deployments for the various providers. Some Kubernetes clusters require an additional deployments required by the seed cloud provider in order to work properly, e.g. Contract: ControlPlane resource with purpose exposure

Controlplane github