Bridge to Kubernetes
With Bridge to Kubernetes, the only thing you need to run and debug on your development machine is the microservice you're working on and your preferred dev tools.
Bridge to Kubernetes extends the Kubernetes perimeter to your development computer allowing you to write, test, and debug microservice code while connected to your Kubernetes cluster with the rest of your application or services. With this workflow, there is no need for extra assets, such as a Dockerfile or Kubernetes manifests. You can simply run your code natively on your development workstation while connected to the Kubernetes cluster, allowing you to test your code changes in the context of the larger application.
Key Features
Simplifying Microservice Development
Eliminate the need to manually source, configure and compile external dependencies on your development computer.
Easy Debugging
Run your usual debug profile with the added cluster configuration. You can debug your code as you normally would while taking advantage of the speed and flexibility of local debugging.
Developing and Testing End-to-End
Test end-to-end during development time. Select an existing service in the cluster to route to your development machine where an instance of that service is running locally. Request initiated through the frontend of the application running in Kubernetes will route between services running in the cluster until the service you specified to redirect is called.
Getting Started Resources
Data and telemetry
Bridge to Kubernetes collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more.
What's New
3.2.20240123.7
- Updating B2K CLI to latest version to support debugging arm64 clusters. Please refer for release notes here
3.2.20231023.6
- Updating to latest b2k CLI version for several improvements and fixes. Please refer for release notes here
3.2.20230819.1
- Updating to latest B2k CLI version majorly for remediating security vulnerability for CBL mariner. Please refer for release notes here
3.2.20230715.6
- Updated to latest B2k CLI version majorly for dotnet 7.0 upgrade. Please refer for release notes here
3.2.20230531.4
- Updated Bridge to Kubernetes to latest CLI version, here are the release notes
3.2.20230505.1
- Updated Bridge to Kubernetes to latest CLI version
3.2.20230331.1
- Updated Bridge to Kubernetes to latest CLI version with various features and bug fixes.
3.2.20230314.5
- Updated Bridge to Kubernetes manager with various bug fixes
3.2.20230223.5
- Updated the Bridge to Kubernetes manager with various bug fixes
- Updated launch profile setting for enabling environment variable based service configuration
3.2.20230202.5
- Updated the Bridge to Kubernetes connection manager with improved support for gRPC and JSON serialization changes
3.1.20230118.1
- Updated the Bridge to Kubernetes connection manager to latest release
3.0.20220912.3
- Fix a regression in Visual Studio 2022 17.3 that caused cluster connections to be immediately disconnected
3.0.20220308.1
- Fix regression in console apps
3.0.20220224.3
- Visual Studio 2022 Support
2.1.20210515.1
2.1.20210411.1
- Add support for liveness/readiness probes
- Support for debugging services backed by stateful sets
- Various bug fixes
Known Issues
- If your cluster hosts multiple headless services, you might encounter connection issues with Bridge to Kubernetes.
2.1.20210327.1
- Fixed an issue that could cause an error parsing available routing endpoints from a Kubernetes cluster
- Updated the routing endpoint field to allow a user to manually specify an endpoint URL even if there was an error retrieving the list of endpoints from a cluster
2.1.20210317.1
- Fixed an issue where a task retrieving resources from the cluster could become blocked if too many resources were returned
- General bug fixes to improve the connection process
2.1.20210227.1
- Fixed an issue where the error "No process is associated with this object" could be reported during service connection
2.1.20210213.1
- Fixed an issue that could cause a connection to hang if the target Kubernetes namespace has a large number of services
2.1.20210129.1
- Fix for an intermittent issue starting the EndpointManager service during cluster connection
2.1.20210126.2
- Fix for an error listing ingress/endpoint urls under certain cluster configurations
2.1.20210121.2
- Support for HTTPS routing endpoints
- Fixed a bug that could cause issues initializing a debugging session with routing isolation support
- Ensured the cluster configuration dialog doesn't extend behind the limits of the screen for lower resolution displays
2.0.20201216.1
- Support for using Bridge to Kubernetes with clusters configured in your local kube config
1.3.20201106.1
- Added support for Azure sovereign clouds
1.2.20201009.2
- Fixed a bug that could cause errors for users with spaces in their home directory path
1.1.20200929.4
- Fixed a bug that could result in an error when debugging immediately after a build completed
- Fixed a bug related to how ASPNETCORE_URLS are handled in the launch profile
- Fixed an occasional file in use error when establishing a connection to the remote cluster
1.0.20200919.1
- Updated branding and extension name to Bridge to Kubernetes
- Improved clarity of error messages
- Improved performance when querying cluster resources
- Fixed a bug where the connection couldn't stop services with conflicting port reservations if there was a space in the name
- Fixed a bug that could prevent a user from re-connecting if they started a new connection session immediately after disconnecting for their previous session
0.1.20200906.1
- Added support for service routing isolation to allow developers to debug a service without interfering with the existing services running in their cluster
- Fixed a bug that prevented the extension from working in Visual Studio 16.8 Preview 2
0.1.20200808.1
- Kubernetes resources are sorted alphabetically in selection dropdowns
- Fixed a bug where the VS toolbar disconnect button wouldn't actually disconnect from the cluster
- Fixed a bug that could prevent a user's Azure subscriptions from loading if one or more account tenants is inaccessible
