You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 11, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 11, 2023. It is now read-only.
We are super excited to announce General Availability of Bridge to Kubernetes.
Formerly known as Local Process with Kubernetes, Bridge to Kubernetes is an iterative development tool offered in Visual Studio and VS Code that allows developers to write, test and debug microservice code on their development workstations while consuming dependencies and inheriting existing configuration from a Kubernetes environment.
Developers using Bridge to Kubernetes can:
Increase efficiency by running code directly on development workstations.
Develop and debug microservice code end-to-end in isolation from teammates.
Separate development workflows from DevOps configuration.
Satisfy external microservice dependencies by connecting to existing services running in the cluster.
Learn how to use Bridge to Kubernetes by following our quickstarts for Visual Studio and VS Code.
Hello, I installed the Bridge to Kubernetes extension on Visual Studio 16.9.4. When I open a .Net Core 3.1 app, I see the Bridge to Kubernetes option on the Start button dropdown. When I open a .Net Framework 4.8 Windows app, I don't see the option. Does Bridge to Kubernetes support .Net Framework Windows apps?
hrkyemba Thanks for your message! Unfortunately, Bridge to Kubernetes doesn't work with .NET Framework because we don't support Windows nodes in Kubernetes. We investigated this possibility a couple of months ago, but unfortunately the cost was too high compared to the number of customers actually targeting this environment (from our discussions most customers using Windows nodes/.NET Framework were porting older apps to Kubernetes).
Would using .NET Core be an option for you?
Thanks for the confirmation. We're working on porting our apps to .Net Core. In the meantime, they are .Net Framework Windows apps. I'm not sure what you mean by "we don't support Windows nodes in Kubernetes", as we've been running our Windows containers in AKS for more than a year. Are you talking about the Bridge to Kubernetes and Dev Spaces not supporting Windows containers?
hrkyemba Thanks for your reply. Yes, when I was saying "we don't support", I was talking about we==Bridge to Kubernetes. Indeed, AKS does support Windows nodes.
Activity
hrkyemba commentedon Jul 8, 2021
Hello, I installed the Bridge to Kubernetes extension on Visual Studio 16.9.4. When I open a .Net Core 3.1 app, I see the Bridge to Kubernetes option on the Start button dropdown. When I open a .Net Framework 4.8 Windows app, I don't see the option. Does Bridge to Kubernetes support .Net Framework Windows apps?
daniv-msft commentedon Jul 9, 2021
hrkyemba Thanks for your message! Unfortunately, Bridge to Kubernetes doesn't work with .NET Framework because we don't support Windows nodes in Kubernetes. We investigated this possibility a couple of months ago, but unfortunately the cost was too high compared to the number of customers actually targeting this environment (from our discussions most customers using Windows nodes/.NET Framework were porting older apps to Kubernetes).
Would using .NET Core be an option for you?
hrkyemba commentedon Jul 9, 2021
Thanks for the confirmation. We're working on porting our apps to .Net Core. In the meantime, they are .Net Framework Windows apps. I'm not sure what you mean by "we don't support Windows nodes in Kubernetes", as we've been running our Windows containers in AKS for more than a year. Are you talking about the Bridge to Kubernetes and Dev Spaces not supporting Windows containers?
daniv-msft commentedon Jul 9, 2021
hrkyemba Thanks for your reply. Yes, when I was saying "we don't support", I was talking about we==Bridge to Kubernetes. Indeed, AKS does support Windows nodes.