search

microsoft / mindaro

Bridge to Kubernetes - for Visual Studio and Visual Studio Code
MIT License
307 stars 106 forks source link

Question: dapr support release date #195

Open Rob623 opened 3 years ago

Rob623 commented 3 years ago

Hi,

I`ve noticed on the project road map, that basic dapr support is already marked as done. Can you please tell me if this feature was released yet? or if not, do you have some estimation on when will it be released?

I've just started a task to find a workaround or another way to debug a process in a local developer k8s cluster, using visual studio 2019, that supports dapr as well. obviously, there's no point in doing that if official support is just around the corner...

Thanks, Robert

daniv-msft commented 3 years ago

Thanks @Rob623 for opening this issue!

I confirm we have the changes ready to support Dapr debugging with Bridge to Kubernetes, and that we will release it shortly. We plan to have them available in VS Code by end of next week, and in Visual Studio 1-2 weeks after that.

If you're willing to try beta bits of our VS Code extension, here is how you can test them:

Please note that VS Code easily loses environment variables if you open a new window, so please make sure that you can see the [STAGING] prefix in the Kubernetes status bar item before testing your application.

Rob623 commented 3 years ago

Thank for the quick reply! Well we generally don't use VS Code as its significantly less powerful than VS. It may be necessary since I also have to support a use case of debugging pods on a local k8s on linux. Although I can remote debug from VS on windows to my pod on the linux machine, remote debug in VS is very limited.

Does BTK have an ability to connect to a remote, on-prem cluster? e.g. local k8s on a linux machine (a private dev env cluster). In other words: I would like to work from VS on my windows machine and debug something running inside a pod on my linux machine. "Bringing" the process to my local machine, like BTK does, is a very good option for most scenarios.

Anyway, regarding the beta: I would try it on VS but as for VS Code probably not, again, since VS Code is not being used. Depends on what solution can I find for the above use-case in the next few days.

daniv-msft commented 3 years ago

Hi @Rob623, Thanks for your reply! No pressure to try the VS Code beta version: it's easier for us to share binaries for VS Code (and in that case, we don't have Dapr support in Visual Studio yet), but I totally understand that Visual Studio works better for you.

Yes, Bridge to Kubernetes support on-prem clusters as well: as long as you have the kubeconfig file to access a Kubernetes cluster, we'll work (both on Visual Studio and VS Code). Please don't hesitate to let me know if you encounter any issues.

Rob623 commented 3 years ago

Thank you, it works!

Rob623 commented 2 years ago

Hi,

Any updates on the visual studio release date for the dapr enabled version?

Thanks, Robert

daniv-msft commented 2 years ago

Hi @Rob623,

Thanks for your message. It seems that I've been too optimistic in my initial estimation of the Visual Studio release including Dapr.

The change has been released in VS Code for a couple of months now. However, it's not available in Visual Studio yet as it implies a fair amount of changes, and we didn't see a huge customer demand for it. We might reevaluate this depending of how much traction this gets in the future, but unfortunately as of today it's hard to justify the investment.

We've just had a presentation of Dapr + Bridge to Kubernetes during the Kubecon, so hopefully this will bring new users that will be interested in this feature.

Rob623 commented 2 years ago

Hi @daniv-msft

Could you shed some light on what are the difficulties? Is there some online discussion record/forum similar that I can read about it?

Since most of the problems to solve should be similar between VS and VSCode, I`m guessing its more in the plugin and/or exact IDE solution area...?

daniv-msft commented 2 years ago

Hi @Rob623, You're right, the work to do here is in the Visual Studio-specific part of our code. The implementation to enable this is not a huge amount of work in itself, but because we prioritize work by customer demand, we're not working on this actively at this point.

The discussion in itself isn't online (because we're discussing things by email/IM and not on a public forum). We might move all this kind of discussion online as well when we open source Bridge to Kubernetes.

Rob623 commented 2 years ago

any news about visual studio support?