Initial implementation #1
Description
I'm pretty far along on this but am going to table the effort for a while.
I've gotten the vs-debug container image working pretty well over in the nforgeio/neonsdk repo and I am able to deploy that as an ephemeral container to the target pod and it appears that the the Visual Debugger is attaching to the process, but pausing the debugger doesn't seem to do anything, even when I have the source solution loaded.
This is going to take some debugging. This was working for the RaspberryDebugger fine, but we were launch the process there, instead of attaching to and existing process. A good place to start would be to see if launching the process works for KubernetesDebugger.
Here's the remaining work items:
- Make attach work
- Remember the current container: we currently remember the current namespace and pod in the current session. Remembering the container too would be nice.
- We don't always get a list of processes when we select a container
- Disable row height sizing in the process grid
- Add some kind of progress indication, since it may take some time for the cluster to download and start the vs-debug ephemeral container
- Revert away from using kubectl port-forward towards our own port forwarding class (which looks like it's working)