Skip to content

Finish migration of Component Controller to V2 backed by resolution service #753

@frewilhelm

Description

@frewilhelm

Description

The Repository and Component Controller currently depends on the old OCM reference library, embedding validation, resolution, and verification logic directly into reconciliation. This causes tight coupling, poor testability, and scaling issues when managing hundreds of repositories and versions.

The goal is to migrate the controllers to use the adjusted Resolution Service, which provides caching, deduplication, and concurrency control. This decouples resolution from reconciliation and aligns with the phased migration strategy.

References:

Done Criteria

  • Remove any leftovers of ocm lib v1
  • Clean abstraction layer for cache/resolution service
  • On cache miss, controller status is updated to Progressing, not blocked on remote call.
  • On cache hit, controller status is updated to Ready with resolved version.
  • Deduplication verified: multiple reconciles for the same version do not trigger duplicate backend fetches.
  • Prometheus metrics expose Resolution latency (histogram)
  • 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)
  • Enduser Documentation updated (if applicable)
  • Internal technical Documentation created/updated (if applicable)
  • Successful demonstration in Review

Prerequisites

Metadata

Metadata

Labels

area/ipceiImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epic

Type

No fields configured for Task.

Projects

Status
🍺 Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions