Deploy docker image wrapping cloud orchestrator

[0405ysj]

No description provided.

[0405ysj]

@ser-io PTAL. HDYT about wrapping CO with docker? Would it be the way we should go, as you mentioned in the mail thread?

[ser-io]

@ser-io PTAL. HDYT about wrapping CO with docker? Would it be the way we should go, as you mentioned in the mail thread?

Thanks for sending this out. Yes, I think it's better to package the CO service into a Docker image for on-premises deployment. I'm still working on the design.

[ser-io]

We need to rephrase the story of this PR.

To do so we need to be clear about containerizing the CO service vs CO as a Docker Instance Manager.

1. The code under scripts/docker is to run the CO as a Docker Instance Manager, we shouldn't modify this code just yet.

2. Under a new deployments/ directory we create the tools/scripts to containerize the CO service, you cannot have a fixed conf.toml here, you need to pass one.

3. Back to scripts/docker, here you can reuse the work in step 2 if you prefer to run a docker container rather than building and running the binary on your own. You can publish artifacts of this specific docker image, but let's don't this just yet.

[0405ysj]

To do so we need to be clear about containerizing the CO service vs CO as a Docker Instance Manager.

Understood. As a following question, would GCP case be using containerized CO in the future? @ser-io

[0405ysj]

Converting this into draft again, since previous review was to get folks' opinions initially & now it's iterating for writing better code.

[0405ysj]

This PR would be paused until sharing design doc from Sergio.

[0405ysj]

After merging this PR, we would be able to deploy Cloud Orchestrator via Artifact Registry.

[ikicha]

LGTM, but @ser-io might want to review this PR as well.