| For debuggers, we wrote a few guides like this one: https://okteto.com/blog/how-to-develop-node-apps-in-kubernet.... > We need to maintain separate profiles for running apps in debug mode, to expose the java debug port to the host and supply the right JVM options Yes, you should. This is something you can do in the 'okteto.yml' file. You can specify different environment variables, different commands and even a different image (e.g. an image with your dev tools and debugger, which you don't need in prod). > Latency This can be a challenge, for sure, specially if you have a bad network connection. In our experience, debuggers and incremental file sync don't require too much bandwidth. > Don't leave your debugger paused for too long This has happened a lot to me. In the latest version we introduced a switch to disable healthchecks during dev time so avoid this. > And forget about trying to debug something that happens on application boot This is the trickiest definitely. I've had luck by pausing the debugger on attach (on go and node you can do this), but it's not the most optimal. |
It would be REALLY COOL to have a one- (or even few-) click IDE integration to attach-debugger-to-instance-deployed-in-Okteto. If you had that, I would already be pitching your product to our head of engineering and asking our head of security to expedite due diligence.
edit: put another way, the pain points you DO currently solve for are ones I don't currently have, because I'm already mostly avoiding them by not running my dev instances in Kubernetes unless I really need to.