Skip to content

Kubernetes Controllers: Implement Component Version Resolution Service #692

@jakobmoellerdev

Description

@jakobmoellerdev

Description

As an OCM developer I want to base my controller rework on an existing component version resolution service I can call safely.

  • Design LRU cache with singleflight + semaphore worker pool
  • Define cache key generation (canonical JSON + SHA-256)
  • Add cache invalidation strategies (event-driven, TTL, negative caching)
  • Integrate metrics (cache hit/miss, queue size, worker pool usage)

Described conceptually by https://github.com/open-component-model/open-component-model/blob/main/docs/adr/0009_controller_v2_lib_migration.md

This should be based on the new OCM Libraries and make use of the component version repository abstraction there.

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)
  • Enduser Documentation updated (if applicable)
  • Internal technical Documentation created/updated (if applicable)
  • Successful demonstration in Review

Metadata

Metadata

Assignees

Labels

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

Type

No fields configured for Task.

Projects

Status
🔍 Review

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions