Merge pull request #2721 from feiskyer/azure-az

Make Azure availability zone KEP to implementable
This commit is contained in:
k8s-ci-robot 2018-09-29 13:45:36 -07:00 committed by GitHub
commit a7276ed0f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 3 deletions

View File

@ -12,10 +12,11 @@ reviewers:
- name: "@colemickens" - name: "@colemickens"
approvers: approvers:
- name: "@brendanburns" - name: "@brendanburns"
editor: TBD editor:
- "@feiskyer"
creation-date: 2018-07-11 creation-date: 2018-07-11
last-updated: 2018-07-11 last-updated: 2018-09-29
status: provisional status: implementable
--- ---
# Azure Availability Zones # Azure Availability Zones
@ -266,6 +267,13 @@ Note that
So if users are planning to migrate workloads to zoned nodes, old AzureDisks should be recreated (probably backup first and restore to the new one). So if users are planning to migrate workloads to zoned nodes, old AzureDisks should be recreated (probably backup first and restore to the new one).
## Implementation History
- [kubernetes#66242](https://github.com/kubernetes/kubernetes/pull/66242): Adds initial availability zones support for Azure nodes.
- [kubernetes#66553](https://github.com/kubernetes/kubernetes/pull/66553): Adds avaialability zones support for Azure managed disks.
- [kubernetes#67121](https://github.com/kubernetes/kubernetes/pull/67121): Adds DynamicProvisioningScheduling and VolumeScheduling support for Azure managed disks.
- [cloud-provider-azure#57](https://github.com/kubernetes/cloud-provider-azure/pull/57): Adds documentation for Azure availability zones.
## Appendix ## Appendix
Kubernetes will automatically spread the pods in a replication controller or service across nodes in a single-zone cluster (to reduce the impact of failures). Kubernetes will automatically spread the pods in a replication controller or service across nodes in a single-zone cluster (to reduce the impact of failures).