The user scenario is a team with a GPU cluster as daily development environment. Currently, the users need to create a pod manually. And if we want to save the resources, it is much more inconvenient for the users to terminate those pods when not used. It would be great if we can leverage the devcontainer and the remote feature (maybe with [the kubernetes extension](https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.vscode-kubernetes-tools)?) of VSCode to manage the lifecycle of pods.

The user scenario is a team with a GPU cluster as daily development environment. Currently, the users need to create a pod manually. And if we want to save the resources, it is much more inconvenient for the users to terminate those pods when not used. It would be great if we can leverage the devcontainer and the remote feature (maybe with [the kubernetes extension](https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.vscode-kubernetes-tools)?) of VSCode to manage the lifecycle of pods.

I notice that it is possible to [attach to a container in a kubernetes cluster]( https://code.visualstudio.com/docs/devcontainers/attach-container#_attach-to-a-container-in-a-kubernetes-cluster) but it lacks the ability of lifecycle management.

_Originally posted by @huxuan in https://github.com/devcontainers/community/discussions/97_