redhat-developer / redhat-developer/vscode-openshift-tools
Provide way to run OpenShift Connector in disconnected environment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the OpenShift Connector invokes odo push and handles extension settings and cluster or init-image availability. Define the setting for the odo init image, the ODO_BOOTSTRAPPER_IMAGE environment value, and the unavailable-image message; done means disconnected odo push flows are supported and configuration guidance is shown when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100