简体繁体 English

Azure Kubernetes 服务 (AKS) 的高可用性/弹性

[英]High Availability/Resiliency with Azure Kubernetes Service (AKS)

原文 2018-08-23 20:44:11 2 3 azure/ high-availability/ azure-aks

Azure Kubernetes Service (AKS) currently does not support availability zones. Azure Kubernetes 服务 (AKS) 当前不支持可用性区域。 What are the ways in which we can achieve resiliency from data center failures while using AKS (Master and Worker nodes)?在使用 AKS（主节点和工作节点）时，我们可以通过哪些方式从数据中心故障中恢复弹性？

One thing i can think of is to have an AKS Clusters in 2 different Azure regions, and have Traffic Manager in front of it.我能想到的一件事是在 2 个不同的 Azure 区域中有一个 AKS 集群，并在它前面有流量管理器。 Any other recommendations, solutions/reference architectures are appreciated.感谢任何其他建议、解决方案/参考架构。

3 个解决方案

A Data Center-wide outage and a Region-wide outage are both low-probability disaster scenarios.数据中心范围的中断和区域范围的中断都是低概率灾难场景。 So having a solution that is resilient against Data Center failures, but isn't resilient against Region-wide issues is probably not a great idea.因此，拥有一个对数据中心故障具有弹性但对区域范围的问题没有弹性的解决方案可能不是一个好主意。 That's why Azure didn't initially implement Availability Zones, instead using Availability Sets.这就是 Azure 最初没有实施可用区，而是使用可用集的原因。

So yes, if you are planning your application seamlessly surviving a disaster, you want to fail over to a seperate region, which would mean a separate cluster and replicated data.所以是的，如果您正在计划您的应用程序无缝地在灾难中幸存下来，您希望故障转移到一个单独的区域，这意味着一个单独的集群和复制的数据。

Azure now supports AKS cluster distributed across availability zones. Azure 现在支持跨可用区分布的 AKS 群集。 follow the link --> https://docs.microsoft.com/en-us/azure/aks/availability-zones按照链接 --> https://docs.microsoft.com/en-us/azure/aks/availability-zones

Ark( https://github.com/heptio/ark ) Can help as opensource for managing at any level. Ark( https://github.com/heptio/ark ) 可以作为开源帮助进行任何级别的管理。 From Azure perspective Azure Traffic Manager to route traffic to the different regions can be mix the configurations for provide an optional implementation.从 Azure 的角度来看，将流量路由到不同区域的 Azure 流量管理器可以混合配置以提供可选的实现。