Provide way to run OpenShift Connector in disconnected environment

[mohitsuman]

Currently OpenShift Connector does not perform any specific action to run in disconnected environment. It should add action calls specific to odo to make it work in disconnected network.

There should be a setting for extension to point to ODO init image and if it is set 'odo push' command should be executed with ODO_BOOTSTRAPPER_IMAGE env variable set to image stream to use from the disconnected cluster.

There should be a way to detect that ODO init image is not available and show the message that suggest to configure ext and cluster for work in disconnected environment.

[mohitsuman]

@dgolovin @kadel Let's discuss more on this in the odo-adapter sync up call.

[crbetts1]

Any progress on this?

[kadel]

What disconnected environment means here? Is the machine where the OpenShift connector is running disconnected or has restricted access to the broader internet? Or is this about the OpenShift cluster being disconnected / having restricted network access?

[crbetts1]

Our OpenShift cluster is disconnected.

I ended up discovering that you can set "terminal.integrated.env.windows": { "ODO_BOOTSTRAPPER_IMAGE": "docker-registry.default.svc:5000/openshift/odo-init-container-rhel8:1.1.9" }, In the settings in vscode and then it will use the odo image that has been manually pushed into the cluster's registry and not from an outside registry.