Epic: Create V2 Service Provider Flux

[In-Ko]

Understand the Epic

After the developer documentation and the template repo are available in a first version (Epic #324), we need to validate this on our own, using one of the next Services we wanted to expose as Service Provider V2: Flux.

Context / Background

• Flux Service Provider V2 is required to reach feature-parity between V1 and V2 Landscapes.
• Flux Service Provider V2 seems to be an ideal candidate to verify the service provider template repository and related documentation.

User Stories or tasks

No response

What is required to accept the Epic as finished.

• TBD
• TBD

Dependencies of this Epic

• Task: Add platform and workload cluster to DomainServiceReconciler in Service Provider Template #404

Risks of this Epic

No response

Known Stakeholders of this Epic

No response

Milestone Definitions for this Epic.

No response

Metrics Definition for this Epic.

No response

Any further valuable resources.

No response

[reshnm]

Before continuing with this item we need to clarify how the general architecture regarding Flux should look like: openmcp-project/docs#23