Provide a way to install individual components/controllers with the OCM CLI including install from dedicate/local OCI registry

souleb commented 1 year ago

UPDATE: On the team meeting the requirements for this ticket was refined and moved to OCM repo/project backlog.

The scope of the ticket is to allow to install individual OCM tooling component/controller with OCM CLI in similar fashion to the MPAS bootstrap command but to allow provision individual components. this includes but is not limited to: flux, ocm-controller, git-controller, replication-controller and the registry. this should also also to specify (local) OCI registry as a component source.

this task should also ensure the cli help and documentation is updated accordingly.

~MPAS is releasing a bootstrap component which contains must of the dependencies(ocm controllers and flux). There is a scenario where only flux and the ocm-controllers are needed. We should provide a flag to enable that scenario.~

souleb commented 1 year ago

cc @morri-son

robertwol commented 11 months ago

@souleb is this now already in place

souleb commented 11 months ago

Not implemented yet.

robertwol commented 11 months ago

@morri-son apparently the requirement come from you.

Could you elaborate on the specific use case.
which components should be installed with the dedicated new flag? (this will override default installed component?)
do we want to specify which components to be installed as a parameters to the option/flag

morri-son commented 11 months ago

Since MPAS contains all components that are required in the basic OCM/GitOps/Flux scenario for the air-gapped scenario, I thought it makes sense to simply use the MPAS cli to for this scenario, too. If we would have the ability to install the required set of components by using an option that would be nice. I'm not sure if we require the ability to specify each of the controllers that should be installed or just the two scenarios, basic and MPAS. I would be fine with the latter. controller to be installed for the basic scenario would be flux, ocm-controller, git-controller, replication controller and the registry I guess.

robertwol commented 11 months ago

On the team meeting the requirements for this ticket was refined and moved to OCM repo/project backlog.

The scope of the ticket is to allow to install individual OCM tooling component/controller with OCM CLI in similar fashion to the MPAS bootstrap command but to allow provision individual components. this includes but is not limited to: flux, ocm-controller, git-controller, replication-controller and the registry. this should also also to specify (local) OCI registry as a component source.

this task should also ensure the cli help and documentation is updated accordingly.

open-component-model / ocm-project

Provide a way to install individual components/controllers with the OCM CLI including install from dedicate/local OCI registry #38