Ide integration

[bhack]

Do you have already any plan on how to integrate with ide?
I.e. atom/atom#14860

[r2d4]

As a weekend project I started https://github.com/r2d4/vscode-k8s, which is available on the visual studio code marketplace at https://marketplace.visualstudio.com/items?itemName=kubernetes-tools.k8s

It exposes a "skaffold dev" and "skaffold run" right-click menu item on skaffold.yaml files, which runs in the integrated terminal.

I don't plan to devote much time to this right now, but I'd be happy to help others get started if theres enough interest.

[bhack]

@r2d4 I think that generally there is a specific issue about language servers and remote debbuger comunication cause dependencies are only available in the image.

[bhack]

I.e. For vscode see microsoft/vscode-python#79

[bhack]

Other than language server and interpreter or execution there is also the remote debugging.
An example for python but still not automated: https://github.com/DonJayamanne/vscode-python-samples/tree/master/remote-debugging-docker

[bhack]

Debugging on compiled language: https://github.com/Microsoft/vscode-cpptools/blob/master/Documentation/Debugger/gdb/PipeTransport.md#docker-example

[bhack]

Probably this cloud be interesting also if it is related to Draft https://github.com/Azure/vscode-kubernetes-tools/

[bhack]

I think that there could be something in common with Skaffold also for the debug requirements vscode-kubernetes-tools/vscode-kubernetes-tools#160

[bhack]

@r2d4 If you don't have enough bandwidth here I think that there could be a collaboration to reuse some common components of https://github.com/Azure/vscode-kubernetes-tools if the Draft part will be pluggable and not embedded. Most of the features there are K8S related. Do you think that there could be some contact between the Azure and Google Container teams about this or is it sci-fi? 😉

[bhack]

/cc @itowlson What do you think?

[bhack]

Check also https://medium.com/solo-io/introducing-kubesquash-remotely-debug-your-kubernetes-pods-f3e3391eaf16

[bhack]

/cc @ilevine

[itowlson]

@bhack At this stage the core team for VS Kubernetes Tools is focused more on Draft than on Skaffold (and, unfortunately, we have limited resource and can't do everything!), but we definitely want to enable folks to plug in additional tools. I'm working surfacing an API from the VS Kubernetes Tools extension that would allow another extension to leverage and integrate with the existing commands an UI. Very happy to work with the Skaffold community on that.

[bhack]

https://blogs.msdn.microsoft.com/visualstudio/2018/06/08/preview-of-visual-studio-kubernetes-tools/

[bhack]

There are two vscode issues to follow about remote scenarios if you are interested:
microsoft/vscode#35671
microsoft/vscode#29194

[nkubala]

@bhack sorry there hasn't been a lot of clarification from the team here, and thanks for all the ideas and input! we're currently working on a number of features to make native IDE integration possible, including schema generation for syntax highlighting of skaffold resources and a full control API exposed over gRPC. you can track these individual features with the ide label on issues in the repo.

[bhack]

Cause you had an initial vscode plugin my feedbacks was almost oriented to vscode and all the features requested for remote interaction cause soon or later you need to interact with pod remote resources for debugging etc..

[nkubala]

with the release of Cloud Code, I think this issue can be closed! @bhack and others please go give it a try, it has awesome native skaffold integration which we're actively developing and improving on.

any cloud code specific issues can be opened on their issues repo, or improvements in skaffold that you think would benefit cloud code can of course be opened here.

[bhack]

@nkubala Do you know if it solve also #1396?
Or is it still in the Skaffold perimeter?

[nkubala]

@bhack I don't think this issue addresses #1396 unfortunately. that will require a separate change to the way we trigger syncs and isn't really IDE specific. an API for controlling specific skaffold components is still on the table though, and we'll look into how we can leverage it to sync to non-skaffold targets.

[bhack]

Ok thanks. I will stay subscribed to #1396 for updates.