In this module, you:
- Created an AKS cluster with an initial e-commerce app.
- Created an ACR instance to publish and deploy an updated microservice to AKS.
- Reviewed some key resiliency concepts.
- Implemented a resilience feature in your app's code using Polly.
- Implemented a resiliency system in your cluster using Linkerd.
Remove Azure resources
It's important that you de-provision the Azure resources used in this module to avoid accruing unwanted charges.
To de-provision all of the resources created in this module, run the following command:
az group delete --name eshop-learn-rg --yes
The preceding command deletes the resource group containing the AKS and ACR resources. Another resource group containing infrastructure resources, such as IP addresses, was previously created on behalf of the AKS resource. This group, and all resources contained within, is also deleted when the AKS resource is deleted.
Revert .NET Core SDK changes
The setup script installs a newer version of the .NET Core SDK, alongside the default SDK version of Cloud Shell. You can choose to keep this configuration. To revert to your prior configuration, run the following command:
cp ~/.bashrc.bak.microservices-aspnet-core ~/.bashrc
The preceding command restores your prior .bashrc profile startup file from a backup saved by the setup script.
Download project files
Use the following command to package and download your project files:
pushd ~/clouddrive/aspnet-learn/src && \ zip -r ~/clouddrive/aspnet-learn.zip . && \ popd && \ download ~/clouddrive/aspnet-learn.zip
Reset Azure Cloud Shell
The scripts used in this module make temporary changes to your Cloud Shell preferences. You don't need to reset your configuration if the scripts ran as intended. To reset your Cloud Shell to its default configuration, see the documentation on deleting personal data.
Learn more about microservices
- Free e-book: .NET Microservices: Architecture for Containerized .NET Applications
- Full eShopOnContainers reference app on GitHub
- Video: Implement microservices patterns with .NET Core and Docker containers
The above video doesn't reflect current .NET Core tooling. However, the architectural concepts and design patterns remain valid.