Deploy container image to cluster

[datho7561]

• Add "Create Deployment from Container Image URL" wizard to project context menu
  • It uses the VS Code text input
  • It has a back button and remembers what you've entered when you go back, similar to what Victor did for the login workflow
  • Once the deployment's been created, the logs for the container are opened in the OpenShift Terminal
• Add demo gif and walkthrough entry for "Create Deployment from Container Image URL"
• Add "Delete" context menu item for Kubernetes objects (eg. Deployments)
• Add "Watch logs" context menu item for Kubernetes objects (eg. Deployments)

Closes #2418

Signed-off-by: David Thompson [email protected]

[datho7561]

@mohitsuman when you have a change, could you please tell me what do you think about this workflow?

[codecov]

Codecov Report

Attention: 97 lines in your changes are missing coverage. Please review.

Comparison is base (025aa38) 33.12% compared to head (baa68eb) 32.81%.
Report is 12 commits behind head on main.

❗ Current head baa68eb differs from pull request most recent head beb234f. Consider uploading reports for the commit beb234f to get more accurate results

Files	Patch %	Lines
src/deployment.ts	10.52%	85 Missing ⚠️
src/explorer.ts	31.25%	11 Missing ⚠️
src/oc/ocWrapper.ts	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3798      +/-   ##
==========================================
- Coverage   33.12%   32.81%   -0.31%     
==========================================
  Files          84       85       +1     
  Lines        6195     6311     +116     
  Branches     1270     1287      +17     
==========================================
+ Hits         2052     2071      +19     
- Misses       4143     4240      +97     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vrubezhny]

Looks and works good,

Please take into account the suggestions listed inline

[vrubezhny]

Some more things to take a look at:

After I deleted the container image I've deployed earlier to my Kind cluster and [updating/rebasing/rebuilding] restarting the OS Tools I see the following error message:

PS: Probably that's because I've left /Deployment-my-fedora-gtk3-mutter-java-node.yaml deployment YAML file opened in editor. I can't reproduce the error after I closed this editor.

[datho7561]

I looked into how Kubernetes handles specifying which ports to expose to the network internal to the cluster. Roland seemed to think this is done as a part of the Docker/OCI image creation (i.e. adding EXPOSE 8080 to the Dockerfile/Containerfile to expose 8080). After some Googling, this seems to be the case. As a result, I don't think that we need to add another step in the wizard to specify the port. If the user wants to expose the container outside of the cluster, they can use the feature Muthu added for creating a Route.

[vrubezhny]

Looks good to me. Thanks!