Gardener Syncer Job

Overview

Gardener Syncer Job is a Cronjob that regularly synchronizes the Seed data from Gardener System to Kyma Control Plane (KCP). The fetched Gardener Seed data for available cloud providers regions is stored inside a ConfigMap.

For more information, see architectural docs.

Prerequisites

• Gardener Syncer Job is running on KCP.
• Gardener Syncer Job is configured to connect to the Gardener System with kubeconfig file.

Installation and Configuration

The Gardener Syncer Job is installed and run as an ArgoCD application on KCP.

For more information about the Gardener Syncer Job installation and configuration, see the installation and configuration documentation.

Usage

The Gardener Syncer Job runs periodically and fetches the current Seed data from the Gardener System.
The fetched data is stored in a ConfigMap named gardener-seeds-cache in the kcp-system namespace.

The seed information, grouped as regions for all available cloud providers, is stored in the config map structured as follows:

apiVersion: v1
data:
  alicloud: |-
    seedRegions:
    - eu-central-1
  aws: |-
    seedRegions:
    - eu-west-1
    - eu-central-1
    - us-east-1
  azure: |-
    seedRegions:
    - westeurope
    - northeurope
    - westus2
    - eastus
    - eastus2
  gcp: |-
    seedRegions:
    - europe-west1
    - us-central1
  openstack: |-
    seedRegions:
    - eu-de-1
kind: ConfigMap
metadata:
  name: gardener-seeds-cache
  namespace: kcp-system

You can check the status of the job by looking at the logs of the CronJob in the Kyma Control Plane. The job will log any errors encountered during the synchronization process. You can also manually trigger the job by running the following command:

kubectl create job --from=cronjob/gardener-syncer-job gardener-syncer-job-manual --namespace kcp-system

Finally, the list of regions with exiting seed information for each cloud provider is available for all interested KCP services like Kyma Infrastructure Manager (KIM) or Kyma Environment Broker (KEB)

Contributing

See the Contributing Rules and architectural docs.

Code of Conduct

See the Code of Conduct document.

Licensing

See the license file.