Description

The following concepts are significantly different in ocm v2:

• OCM context
• Resolvers
• Verification
• Config lookup

The current behaviour essentially all configuration is done at the beginning of each reconciliation loop. Here, the credentials, the resolvers, the signature validation public keys are read from config maps and secrets and applied (in other words, stored) in the ocm context which is then being passed around.

Since the general serialized configuration types will stay the same, the user API is expected to stay consistent. The code for setting up and passing around the configuration is expected to change though, since the ocm context and ocm config API is different.

Goals:

• Resolve all OCM Config References in the current CRDs into a big yaml
• Use this yaml as baseline for any lookup of component version or resources.
• Completely skip the need for https://github.com/open-component-model/open-component-model/blob/main/kubernetes/controller/internal/ocm/context_cache.go for now, concentrate only cache key stabilization required for the component version resolution service (reuse https://github.com/open-component-model/open-component-model/blob/main/kubernetes/controller/internal/ocm/hash.go#L93 if possible)

Done Criteria

• internal/* includes a package for using ocm lib v2 ( separate packages have been created for the new code )
• 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