Azure Dev Spaces allows developers to quickly and iteratively develop applications running in AKS by enabling changes to be instantly applied to running containers without rebuilding images. Developers can work directly in their own development spaces within a shared AKS cluster and see changes immediately. Dev Spaces handles routing requests to the proper development namespace and provides tracing between services for debugging.

4. Azure Dev Spaces
Fast, iterative development for AKS

5. AKS
with Dev Spaces</>
Edit code with
your favorite editor
SCC =>
CI/CD
Commit
code
Deploy
Iterate fast, directly in Azure
Edit content (html, css, cshtml) Update file directly in running container
Edit server code Restart node service, dotnet build/run
Edit Dockerfile, Helm chart
package.json...
Rebuild container image, redeploy

9. Microsoft Confidential

10. Microsoft Confidential
Microservices are hard to develop locally
Local Development Machine
Azure
Frontend Hotels Promotions Promotions DB
Hotels Promotions Promotions DB
SCC => CI/CD
Traditional Integration Environment
*
*
Test Staging Production
VS / VSCode / CLI

11. Microsoft Confidential
Microservices are hard to develop locally
Local Development Machine
Azure
Frontend Hotels Promotions Promotions DB
Hotels Promotions Promotions DB
SCC => CI/CD
Traditional Integration Environment
*
*
Test Staging Production
VS / VSCode / CLI
Assumptions
1. I know the full
dependency graph
2. I know how to build and
run dependencies
3. I can run it all on my
laptop
Or, create mocks?

12. Microsoft Confidential
Collaborate in a team’s AKS cluster
Lisa's Development Machine
Azure
Frontend Hotel Promotions Promotions DB
VS / VSCode / CLI
SCC => CI/CD
Team's AKS cluster
*
Frontend *
John's Development Machine
VS / VSCode / CLI
SCC => CI/CD
*
*
Hotel *
Test, Staging,
Production
Lisa's “Space” John's “Space”
Dev-Space: John Dev-Space: John
Promotions

14. https://frontend.bd0cfb25...aksapp.io
https://susie.s.frontend.bd0cfb25...aksapp.io
Susie Walter

15. az ads prep

16. Microsoft Confidential
Client synchronizes code to Azure Dev Spaces
Helm chart is installed with instrumentation
Suppose browser calls hotels calls promotions:
- GET http://lisa.s.sh360.abcd.aksapp.io/hotels-api
- GET http://promotions/api/3
- DNS resolves to promotions.mainline
- Proxy notices “dev-space: lisa” and
retargets to IP of promotions.lisa
- Proxy reports traces back to client
Azure use this text to move Azure
hotels
mainline
promotions
mainline
promotions
lisa
“mainline”
namespace
“lisa”
namespace
Azure Kubernetes Service (AKS) thisas
init
Development
Client
azds up helm install
source code is
volume mounted
GET /api/3
HTTP/1.1
Host: promotions
dev-space: lisa
10.2.3.4
10.5.6.7
AKS
Ingress
(nginx)
Proxy sees “lisa.s.” prefix in
host name and adds “dev-
space: lisa” HTTP header
before forwarding the request
to user code
“kube-system”
namespace
routing/tracing proxy
inbound
outbound
routing/tracing proxy
inbound
outbound
routing/tracing proxy
inbound
outbound
Azure Dev Spaces
Browser GET /hotels-api
Init container
builds the
container image

17. 'up' or F5 debug
values.dev.yaml
Luana
namespace
Dev Spaces enabled
Tim
namespace
Dev Spaces enabled
Sanjay
namespace
Dev Spaces enabled
Integratio
n
namespace
Dev Spaces enabled
Productio
n
namespace
CI/CD pipeline
Source control
git commit
git push
Container registry
helm upgrade --
install
values.int.yaml
Luana
Tim
Sanjay
helm upgrade --install
values.prod.yaml

19. Sign up for private preview
aka.ms/devspaces