Task: Implement the deployment controller

[reshnm]

Understand the Task

Description

Implement the reconcile logic of the deployment controller.
In the future, the deployment controller should be able to reconcile any provider type. The scope of this task is to implement a first MVP. For this MVP, it is ok to reconcile a small set of types, in order to quickly validate the approach.

We start with the following scope:

• Gardener Cluster Provider
• Service Provider Landscaper
• (Project Workspace Operator?)

The deployment controller needs to create, update and delete deployments. Focus should be the create and update operations, delete might be coming a bit later.

Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

• Code has been reviewed by other team members
• Internal technical Documentation created/updated
• New / changed code is documented
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated
• Enduser Documentation updated (if applicable)
• Successful demonstration in Review

[robertgraeff]

June 30

The deployment controller can reconcile ClusterProviders, ServiceProvider, and PlatformServices (i.e. not just the Cluster Provider Gardener, or Service Provider Landscaper). The reconcile executes the init command in a job and the run command to deploy the provider.

There are unit tests, which check the install/uninstall of a clusterprovider/serviceprovider/platformservice. The unit tests use the test environment from controller-utils.

Latest changes:

• Cleanup of the pods of the init job
• Pass environment variables to the commands (OPENMCP_PROVIDER_NAME: name of the provider resource, OPENMCP_PLATFORM_CLUSTER_NAMESPACE: namespace in which the provider runs on the platform cluster)
• Print columns (kubectl get shows the phase of the provider)

[In-Ko]

Done, can be closed.