none
Azure Kubernetes Service Shutdown RRS feed

  • Question

  • 1. How can i shutdown my kubernetes cluster service ? I want to bring down and bring up my kubernetes cluster for my env when ever i need .How can i achieve this ? Can anyone help with this  
    Friday, January 18, 2019 4:42 PM

All replies

  • Clusters are not designed to be shutdown and spun up again. Instead when you no longer need you cluster you would just remove it. And if you wanted to spin it back up you could simply deploy a new cluster from the same image. 

    I would suggest you dig around our AKS documentation to get a better understanding of the life cycle of AKS and its uses

    https://docs.microsoft.com/en-us/azure/aks/?view=azure-cli-latest

    Saturday, January 19, 2019 12:00 AM
    Owner
  • Thank you for the response. From the above , i believe if we remove and create new cluster again then we have to create or associate new service principal of a cluster with the ACR to pull images and it would take time to configure again . My concern is if we remove and deploy new cluster again it would take more time and we have to retain same continuos logs and data that does't happen when we deploy new cluster again. I was looking forward can we stop/start kubernetes service  as like bringing up VM and Down when required. Please let me know if some where am wrong with my hypothesis.

    Q. Stopping my cluster VM's would cause any problems ? 
    Monday, January 21, 2019 8:13 AM
  • AKS is not designed to be shutdown and started back up like a normal VM would. Although we do create a Node and container for you on the backend you would want to manage all the cluster operations via AKS not not manually through the node itself. That is a big reason as to why we create a separate resource group to store the cluster resources. That way you don't accidentally mess anything up by manually making changes. So for example, you would not want to simply shutdown the node associated with your cluster as it could put the cluster itself in a failed state in which you then would have to recreate anyways. 

    I would suggest you start with these docs to get a better understanding of AKS and how it works for workloads

    https://docs.microsoft.com/en-us/azure/aks/concepts-clusters-workloads
    https://docs.microsoft.com/en-us/azure/aks/best-practices
    https://docs.microsoft.com/en-us/azure/aks/faq

    Also, for persistent storage in AKS you can create persistent volumes that are attached to clusters so you don't lose any data if you remove a cluster or change out nodes. 

    https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv

    AKS works kind of like scalesets. You will have a number of nodes and each node will have containers running your application. If you need more nodes you can scale the cluster and the platform will automatically add the nodes and create the containers. Same thing if you need to scale down. If you ever have an issue with a node the platform should recognize it and remove that node and replace it with a new one. 

    AKS is designed as a highly available service so shutting down your cluster is not something that really fits into that design. You can of course remove containers and keep your cluster up and running but when you want to add an app back you would deploy it again. 

    As per adding the service principal, yes I believe you would have to add that if you recreate a cluster. This would be more time consuming if you are constantly removing and creating new clusters. But besides a dev environment it is assumed you are keeping your service up 24/7

    Tuesday, January 22, 2019 8:06 PM
    Owner