cloudshell addon for in-cluster web terminal
vorburger opened this issue · comments
Would having a web-based terminal running in-cluster be a welcome addon to minikube?
I toyed with this in https://github.com/vorburger/cloudshell/ (not with minikube, yet; just the basis).
The workflow I imagine is minikube addons enable cloudshell; minikube addons open cloudshell and your browser would take you to a shell to runs "in-cluster" from where you could use kubectl (which would already be included in that shell) and what not.
It would also be neat if, after basics are there, one could develop code inside that shell, and build containers (ideally without Using the Docker daemon, but with building root less inside the cloudshell), push to a registry in the cluster, and run.
Is this effectively a web based version of minikube ssh, or is this something bigger?
FYI - the project name conflict with Google Cloud Shell is going to make this super confusing if made into a minikube addon. We'd probably need to call it vorburger-cloudshell or something else.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.