Red Hat signed release for oadp-cli binaries

[Joeavaikath]

We need a way to have a downstream build of the binaries.
This is required, as only this can be served to customers on the OpenShift console.

Downstream release -> Figure out how to host on the cluster (much like oc does right now)

[weshayutin]

1. build the client for mac, windows, linux in the https://github.com/migtools/oadp-cli repo
2. push container to quay
3. from the oadp-operator, host a container that serves the built artifacts e.g. https://downloads-openshift-console.apps.wdharm420.migration.redhat.com/

[weshayutin]

k.. so DockerFile is here:
https://github.com/openshift/oc/blob/main/imagmeees/cli/Dockerfile.rhel

and oadp-operator service example would be here:
https://github.com/search?q=org%3Aopenshift+%22Name%3A+downloads%22+AND+%22Namespace%3A+openshift-console%22+AND+%22Kind%3A+Service%22&type=code

@kaovilai sound right?

[kaovilai]

Yes. copying from slack, there are more dockerfile involved.

if we wanna clone oc team..
image1: we would do cross build inside the container where base image is golang builder as oadp-cli-artifacts
in each single arch image would contain binaries for all supported os/arch ie. we only need a single container arch build because we just need resulting binaries for copy
image2: then have a dockerfile w rhel base image which copy from oadp-cli-artifacts as downloads-image
deployment/service: then in the downloads deployment using downloads-image
serve the content copied earlier

[Joeavaikath]

So oadp-operator will have a deployment and service running to point to this binary server
Will need to stand up the ConsoleCLIDownload and route during operator startup, since route url is dynamic
Working on that second part rn

[kaovilai]

cool. the server itself can be the one creating the ConsoleCLIDownload once ready/running.