VSCode as kubectl editor is not returning to terminal until I quit VSCode completely

[parveenksharma]

On my mac Ventura in my ~/.bash_profile I have :
export KUBE_EDITOR='open -a "Visual Studio Code" --wait'

and it is opening the new VSCode window with command on terminal:
kubectl edit pod fooapp

The problem is once I am done editing the yml and save it and close the associated VSCode window the control is not returning to terminal.
For that I have to Quit VSCode completely.

This is very inconvenient as this is resulting in closing all my other open / work in progress files with VSCode .

Please suggest.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[ardaguclu]

/kind support
/remove-kind bug

[brianpursley]

@parveenksharma

Do either of these work better?

export KUBE_EDITOR='open -a "Visual Studio Code" --wait --new-window'

export KUBE_EDITOR='code --wait --new-window'

[mpuckett159]

I suspect that Visual Studio Code is doing something that prevents kubectl from detecting if the window that was spawned is ever closed, and so it thinks that the edit is still in progress and you have to kill the entire VSCode process to get it to see that the window is closed. This feature was created quite a while ago and I think it expects there to be separate process or something that it can watch to stop and the way VSCode works doesn't allow for that. If these suggestions that Brian made don't work, I don't think we can accomadate how VSCode works unfortunately.

/close

[k8s-ci-robot]

@mpuckett159: Closing this issue.

In response to this:

I suspect that Visual Studio Code is doing something that prevents kubectl from detecting if the window that was spawned is ever closed, and so it thinks that the edit is still in progress and you have to kill the entire VSCode process to get it to see that the window is closed. This feature was created quite a while ago and I think it expects there to be separate process or something that it can watch to stop and the way VSCode works doesn't allow for that. If these suggestions that Brian made don't work, I don't think we can accomadate how VSCode works unfortunately.

/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-sigs/prow repository.