Skip to content

Spike: Component Dependencies (Follow-Up to Spike #167) #572

Description

@rebEllieous

During the spike initiated under ADR-011 "component-dependencies", we documented a proposed solution to ingest OCM ComponentReferences and represent them as distinct ComponentVersion records within the Solar catalog. Following team discussions, the proposed design was deemed too complex to handle purely within Solar's internal controllers. We concluded that handling most of these lifecycle and dependency management problems upstream is the superior solution.

We brought our questions and friction points to the OCM community call. The current status from the OCM maintainers is: the project is not hard-committed to a definitive execution path for runtime dependencies yet; the landscape remains open for discussion.

To implement Dependency Managemement in a way tot benefit both OSCP as well as ODD we are focusing on upstream implementation by extending ocm-kit. This way we have a base to present to and continue working with the ocm team and include this feature as part of ocm-kit in ocm v2.

For this purpose we have opened PR #60 which cointains an rfc outlining a component schema declaring required and provided capabilities / ressources.

ACs:

  • review the OCM-Kit RFC, include oscp into the discussion to make sure their requirements are being met
  • implement PoC in OCM-Kit for one Solar usecase (e.g. CertManager)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestspikeA task to research a question and resolve problems

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions