10.1 Using Azure Dev Spaces and AKS
We have enabled Dev Spaces support for eShop!
Please go to official devspaces doc. You should be familiar with:
- Enabling devspaces to a cluster
- Creating a devspace
- Creating a child devspace
- Deploy to a devspace
az extension add --name dev-spaces-preview
az aks use-dev-spaces -g your-aks-devspaces-resgrp -n YourAksDevSpacesCluster
Once devspaces tooling is added, type azds --version to get the version of DevSpaces tooling.
Tested DevSpaces tooling version was:
Azure Dev Spaces CLI (Preview)
0.1.20190320.5
API v2.17
Future versions should work, unless they introduce breaking changes.
From a Powershell console, go to /src folder and run prepare-devspaces.ps1 (no parameters needed). This script will copy the inf.yaml and app.yaml files from /k8s/helm to all project folders. This is needed due to a limitation of devspaces tooling used. Note that the files copied are added in .gitignore.
If you want to deploy a project to a specific devspace, just go to its source folder (where .csproj is) and type azds up. This will deploy the project to the current devspace.
Due to the status of devspaces today, Web SPA do not use Dev Spaces (so, you can't deploy the SPA in devspace).