Summary
In our example scenario, you needed to support an operating platform by managing the application state while using Kubernetes on Azure Kubernetes Service (AKS).
By creating a new instance of Azure Cosmos DB, you delegated the management of the database to Azure. The application can grow across many regions in the world without any added complexity. Now, your cluster has a better handling of application states. Your cluster is also scalable to the point where you can handle multiple users without needing to configure the database.
Clean up resources
In this module, you created resources using your Azure subscription. You'll want to clean up these resources so that you won't continue to be charged for them. You can delete resources individually, or delete the resource group to delete the entire set of resources.
Navigate to the Azure portal.
Select Resource groups > rg-ship-manager.
On the Overview tab of the resource group, select Delete resource group.
Enter the name of the resource group to confirm. Select Delete to delete all of the resources that you created in this module.
Repeat the preceding steps for the resource group named MC_rg-ship-manager_ship-manager-cluster_eastus to delete all created resources.
Remove the deleted cluster's context using the
kubectl config delete-context
command. Remember to replace the name of the cluster with your cluster's name.kubectl config delete-context ship-manager-cluster
If the command is successful, it returns the following example output:
deleted context ship-manager-cluster from /home/user/.kube/config
Learn more
To learn more about Azure Kubernetes Service, see the following articles:
- Introduction to AKS
- AKS documentation
- AKS production baseline
- Deploy an AKS cluster
- Storage concepts with AKS