Description

Implement a Deployer using kro. This will eventually supersede #146, if the implementation works as expected.

The implementation is based on the findings from #164.

TODOs:

• Remove Storage implementation

• Remove localisation controller

• Remove configuration controller

• Create new OCM Deployer API

  • Takes a reference to a resource that points to a ResourceGraphDefinition and deploys it

• Adjust current component API and controller

  • How do we publish the component-descriptors?
    • Do we even want to do this anymore?
      • Pro:
      • We could store the info in the status (could get big)
      • Con:
        • If we do that in the resource controller, then we have to redownload (and verify) every descriptor on a resource reconciliation (could be exhaustive)

• Adjust current resource API and controller

  • Remove OCI Artifact and replace it with a location (e.g. reference [to an OCI repository/artifact, Helm Repository, GitHub Repository, ...])

• Adjust e2e test with kro

  • Test with FluxCD
    • Simple: Deploy PodInfo with Helm and Kustomize
    • Localisation: Deploy PodInfo but replace image location in the deployment with a reference from a resource (from the OCM component that is available in the cluster as resource).
    • Configuration: Configure values using references from other k8s resources and a kro instance

• Propagate status from RGD to Deployer (superseded to Propagate RGD status to OCMDeployer status #192)

• Adjust deployment kustomization

Done Criteria

• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Successful demonstration in Review