I'm going to check out your product on the weekend. It looks pretty neat. But it would be cool to hear a bit more about how you achieve some of your stated claims. Particularly working with debuggers. The kubernetes/minikube setup at my current role seems downright hostile to debugging - * We need to maintain separate profiles for running apps in debug mode, to expose the java debug port to the host and supply the ri…
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 diff…
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.