Internal technical Documentation created/updated (Create ADR)

[frewilhelm]

Further questions:

• Will replication always only work on the latest or on all in spec (SemVer of Component status)?
• Should a successful replication automatically result in creation of a component and resource CRs?
• How many replication attempts do you want to keep in replication CR status?

[ikhandamirov]

More to follow up on:

• Extend config type transport.ocm.config.ocm.software to support more options of ocm transfer componentversions?
• Is it Ok that when replication is triggered the component is re-downloaded from the source registry?
• Does the replication have to re-run, if transfer options change, but not the component version? If so, the controller needs to be able to detect that change.
• Does an SRE need to be able to see in the status, which transfer option an individual run was executed with? If so, the transfer options likely need to have a dedicated field in the Spec and in the Status.
• How to supply --lookup to the controller: via ocmconfig? Or should the Replication CR refer to several source OCMRepositories (in addition to source Component)?
• Should a Replication support several target OCMRepositories? Alternatively, if a component needs to be replicated to several targets, several respective Replication CRs would need to be created, which likely would be simpler from ops perspective.

[dee0]

Hello @frewilhelm

I have a question about the above diagram. In SAC we are hoping to move to OCM-Controller+Flux for deployment and we are anticipating that the deployment controllers would only be on MCP.

However the diagram above appears to show things not working as we hoped. Or perhaps it it not related to our case?

[frewilhelm]

Hi @dee0, the diagram only shows one possible setup. The setup you are describing is another use-case that will work as well using the kubeconfig fields in Flux to remotely deploy into the runtime clusters.

[jakobmoellerdev]

We now move to the review phase as most ADRs are initially created and in phase of constant feedback. We plan to slowly move ahead with the merge after incorporating feedback.