Azure Dev Spaces is retiring on 31 October 2023

[greenie-msft]

Azure Dev Spaces is retiring on 31 October 2023.

Azure Dev Spaces will be retired on October 31, 2023. Developers should move to using Bridge to Kubernetes, a client developer tool.

The purpose of Azure Dev Spaces was about easing developers into developing on Kubernetes. A significant tradeoff in the approach of Azure Dev Spaces was putting extra burden on developers to understand Docker and Kubernetes configurations as well as Kubernetes deployment concepts. Over time, it also became clear that the approach of Azure Dev Spaces did not effectively decrease the speed of inner loop development on Kubernetes. Bridge to Kubernetes effectively decreases the speed of inner loop development and avoids unnecessary burden on developers.

The core mission remains unchanged: Build the best developer experiences to develop, test, and debug microservice code in the context of the larger application.

How does this affect me?
After 31 October 2023, Azure Dev Spaces will no longer be supported, and all projects using Azure Dev Spaces will no longer function.

What action should I take?
Transition to Bridge to Kubernetes. More information on migration options is available here.

[ahaeber]

The tool azds prep has been helpful to quickly generate Dockerfiles and Helm chart templates for a project. Will that tool continue to exist somewhere?

[greenie-msft]

Hi @ahaeber,

Thank you for your question.

Generating a Dockerfile and Helm Chart is not a capability Bridge supports. We encourage customers to leverage their own practices and tooling for deploying their application to Kubernetes. Bridge enters the picture once the application is successfully running in the cluster.

With that said, the existing Azure Dev Spaces tooling will continue to work for the foreseeable future. You can use the azds prep command without having to provision Dev Spaces in your cluster.

[jadams74]

Fix Azure DevOps Pipline -> Deploy to Kubernetes - Review App with Dev Spaces. This is an out of the box pipeline with Azure Dev Ops and is now broken.

2021-05-20T16:02:01.9216709Z azds : The term 'azds' is not recognized as a name of a cmdlet, function, script file, or executable program.
2021-05-20T16:02:01.9217580Z Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2021-05-20T16:02:01.9218250Z At /home/vsts/work/_temp/azureclitaskscript1621526500059_inlinescript.ps1:5 char:15
2021-05-20T16:02:01.9221075Z + $hostSuffix=$(azds show-context -o json | ConvertFrom-Json).controlle …
2021-05-20T16:02:01.9221626Z + ~~~~
2021-05-20T16:02:01.9222546Z + CategoryInfo : ObjectNotFound: (azds:String) [], ParentContainsErrorRecordException
2021-05-20T16:02:01.9223127Z + FullyQualifiedErrorId : CommandNotFoundException
2021-05-20T16:02:01.9490440Z ##[error]Script failed with exit code: 1