Share via

Node pool automatic failover or not when zone down, config is node-count : 1 , zone: 1 2 3

samartcha.m 0 Reputation points
2024-01-07T14:26:38.4533333+00:00

My customer need to optimize cost but need node recovery when zone down. so what happen when zone down with this configuration

AKS Node pool
node count: 1
zones: 1,2,3

node will be automatic move to other zone or not

Azure Kubernetes Service
Azure Kubernetes Service

An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.


1 answer

Sort by: Most helpful
  1. vipullag-MSFT 26,537 Reputation points Moderator
    2024-01-08T04:51:30.94+00:00

    Hello samartcha.m

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    In AKS, when you configure multiple availability zones for your node pool, it provides high availability by distributing nodes across those zones.

    If you have an AKS node pool with a node count of 1 and the pool is deployed across three availability zones, then if one of the zones goes down, the node in that zone will also go down. In this case, the node will not be automatically moved to another zone.

    To ensure high availability and resiliency, it is recommend that you deploy your AKS node pools across multiple availability zones. If you have a node pool with a node count of 3 and the pool is deployed across three availability zones, then if one of the zones goes down, the two nodes in the other zones will continue to run your workloads.

    You can also use the AKS cluster autoscaler to automatically adjust the number of nodes in your node pool based on demand. This can help you optimize costs while ensuring that you have enough nodes to handle your workloads.

    Hope this helps.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.