🌱 Start ocm env using clusteradm

[qiujian16]

Summary

Related issue(s)

Fixes #

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiujian16

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qiujian16]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[qiujian16]

/assign @zhujian7

[zhiweiyin318]

/lgtm

[zhiweiyin318]

/lgtm

[zhujian7]

/lgtm

[zhujian7]

@dhaiducek @mprahl FYI: I know there seems to be a policy repo that uses the cloning ocm repo and executing make commands to install an ocm env, which is error-prone, here is an example of using the clusteradm to set up an ocm env for your reference, hope this is helpful.

[dhaiducek]

@zhujian7 Thanks for tagging us! clusteradm could be a good solution and we'd definitely be on board for a more reliable build, but for our use-cases:

• We want to be able to deploy stolostron-specific code/images from a particular version (which I'm not sure would be quite as simple with clusteradm?)
• We want test against the latest images rather than a specific version

Would both of these be straightforward with clusteradm also?

[zhujian7]

@dhaiducek I am not quite sure if this is what you need, but you can have a try.
there are --bundle-version='xx' and --image-registry='xxx' options for the clusteradm init and clusteradm join commands.