Carve-out Crossplane from V1 control-plane-operator

[In-Ko]

Understand the Task

Description
Let's have a Spike (time-boxed 3 days!) to find out how we go forward with getting the existing V1 crossplane provider consumable in the V2 architecture within Q3/25.

We outlined three options:

1. Carve-out specific providers from the existing V1 control-plane-operator (e.g. Crossplane)
2. Adapt the existing V1 crossplane provider to be V2-compliant
3. Use the V1 crossplane "as-is" also in our first V2-based deliveries

It was suggested to try (1) first and carve-out Crossplane, to get a feeling of how fast such a carve-out can be done. If it is relatively easy to do, we could go ahead with this approach.

Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

• Spike finished
• Results summarised in a tiny ADR
• Demonstration in Review or Dev-Sync

[maximiliantech]

I demonstrated the functionality in the review on 25/08/2025.
The basic functionality is working and carve-out is finished. There are some bugs and feature requests that I encountered. These is a list of follow-up tasks:

• MCP Service Account: forbidden to grant Crossplane RBAC permissions service-provider-crossplane#21
• Make lables configureable control-plane-operator#104
• fix: function IsCRDNotFound should also work with NoResourceMatchErrors control-plane-operator#105

With that, I would close this issue.