Task: refactor v1-v2 bridge in MCP Operator #228
Description
Understand the Task
Description
Basically, we want to refactor the way the cluster management with the v1-v2 bridge in the MCPO works.
Currently, the APIServer component has two code paths, one for v1 (where it manages the MCP shoot cluster directly) and one for v2 (where it creates a ClusterRequest and AccessRequest). OIDC access and role bindings are done by the Authentication and Authorization components, respectively.
We want to refactor this, so that instead of creating APIServer, Authentication, and Authorization components, the MCP controller creates an MCPv2 out of the MCPv1. The MCPv2 controller handles all tasks that the three aforementioned components did in the v1 architecture.
A minor problem is that the v1 services depend on these components, so the new bridge logic would need to either fake the three components with their corresponding status, or adapt the depending logic in the service controllers. Since v1 has only two services (Landscaper and CloudOrchestrator), the second approach is probably the easier one.
Any further valuable resources.
This is a follow-up issue for #218. Look there for a more detailed description of what we want to do and why.
We can postpone this task a bit, it is not urgent. However, we should get it done before people start using the bridge (currently disabled on all landscapes except for dev), because otherwise we would have to do an additional migration.
What is required to accept the Task as done.
Done Criteria
- Implement MCPv2 generation out of MCPv1 resource
- Adapt dependency logic, so that the services work in v1 and with the bridge
- Write unit tests
- Show in review