Summary

  • 2 minutes

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 database management 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.

  1. Delete the rg-ship-manager resource group that you created for this module. This action deletes all of the resources that you created in this module, including the AKS cluster and Azure Cosmos DB account.

    az group delete --name rg-ship-manager --yes --no-wait

    When the resource group is deleted, the MC_rg-ship-manager_ship-manager-cluster_eastus that contains the cluster's resources is also deleted.

  2. Remove the deleted cluster's context using the kubectl config delete-context <clusterName> command.

    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: