Enhancements: Azure Availability Zones

[feiskyer]

Feature Description

• One-line feature description (can be used as a release note): Add support of Azure Availability Zones.
• Primary contact (assignee): @feiskyer
• Responsible SIGs: sig-azure
• Design proposal link (community repo): https://github.com/kubernetes/community/pull/2364
• KEP: 20180711-azure-availability-zones
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @khenidak
• Approver (likely from SIG/area to which feature belongs): @brendandburns
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (1.12)
  
  
  • Beta release target (1.13)
  
  
  • Stable release target (1.15)
  
  

[feiskyer]

/sig azure
/sig storage

[feiskyer]

/milestone v1.12

[justaugustus]

@feiskyer --

It looks like this feature is currently in the Kubernetes 1.12 Milestone.

If that is still accurate, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y)
  
  
  • Beta release target (x.y)
  
  
  • Stable release target (x.y)
  
  

Set the following:

• Description
• Assignee(s)
• Labels:
  
  
  
  • stage/{alpha,beta,stable}
  
  
  • sig/*
  
  
  • kind/feature
  
  

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/kind feature
/stage alpha

[zparnold]

Hey there! @feiskyer I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[msau42]

Doc placeholder for only the topology-aware dynamic provisioning part: https://github.com/kubernetes/website/pull/9939 (not for the entire feature)

[justaugustus]

@feiskyer --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[feiskyer]

@justaugustus Yep, codes have been merged now and docs will be added to https://github.com/kubernetes/cloud-provider-azure

[justaugustus]

Thanks for the update!

[claurence]

Kubernetes 1.13 is going to be a 'stable' release since the cycle is only 10 weeks. We encourage no big alpha features and only consider adding this feature if you have a high level of confidence it will make code slush by 11/09. Are there plans for this enhancement to graduate to alpha/beta/stable within the 1.13 release cycle? If not, can you please remove it from the 1.12 milestone or add it to 1.13?

We are also now encouraging that every new enhancement aligns with a KEP. If a KEP has been created, please link to it in the original post. Please take the opportunity to develop a KEP

[feiskyer]

It's already part of KEP, https://github.com/kubernetes/community/pull/2364. Let's keep it in v1.13.

/milestone v1.13

[spiffxp]

@feiskyer what work is being done in k/k for this as part of v1.13? are there issues or PR's we could link to for tracking?

[feiskyer]

@spiffxp Yep, we're validating the use cases and hoping to fix issues if there are. But there're no PRs yet.

[AishSundar]

@feiskyer does that mean you are essentially code complete for Alpha in 1.13 and currently validating the flow? or is there any known pending work?

[feiskyer]

does that mean you are essentially code complete for Alpha in 1.13 and currently validating the flow?

Alpha in 1.12 and beta in 1.13.

Seems state doesn't update yet.

/stage beta

[tfogo]

Hi @feiskyer, will there be any updates to the docs necessary for 1.13? The deadline for placeholder PRs for the 1.13 release is November 8. So it's important to make a docs PR as soon as possible if needed.

[feiskyer]

No docs are required in this release. Thanks.

[kacole2]

@feiskyer is there a k/k PR we should be tracking yet going into code slush?

[AishSundar]

From offline sync with @feiskyer, all PRs needed to go into k/k are done. Tests are being developed in a standalone repo https://github.com/kubernetes/cloud-provider-azure and are not bound by Code freeze

[claurence]

@feiskyer Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work/status (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP - it looks like this has this KEP https://github.com/kubernetes/enhancements/blob/master/keps/sig-azure/0018-20180711-azure-availability-zones.md - let me know if that is not accurate. Thanks!

[feiskyer]

yep, it's being tracked by the KEP 18, and it'll still be in beta stage in v1.14.

[claurence]

@feiskyer any PRs we should track for 1.14?

[feiskyer]

@claurence not yet.

[claurence]

@feiskyer ok! Thanks - given there are no PRs and this issue isn't graduating I'm not going to track it on the 1.14 enhancements sheet

[kacole2]

/milestone clear

[kacole2]

I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[feiskyer]

yep, this is on tracked.

/milestone v1.15

[kacole2]

@feiskyer, we're doing a KEP review for enhancements to be included in the Kubernetes v1.15 milestone. After reviewing your KEP, it's currently missing test plans and graduation criteria which is required information per the KEP Template. Please update the KEP to include the required information before the Kubernetes 1.15 Enhancement Freeze date of 4/30/2019. Thank you

[kacole2]

@feiskyer, Enhancement Freeze for Kubernetes 1.15 has passed and this did not meet the deadline. Still missing Test Plans and Graduation Criteria from the KEP. This is now being removed from the 1.15 milestone and the tracking sheet. If there is a need for this to be in 1.15, please file an Enhancement Exception. Thank you. @claurence

/milestone clear

[feiskyer]

/milestone v1.16

[evillgenius75]

Hi @feiskyer , I'm the 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[feiskyer]

@evillgenius75 Yep, and it has already added v1.16 milestone.

[simplytunde]

Hey, @feiskyer I'm the v1.16 docs release lead.

Does this enhancement (or the work planned for v1.16) require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.16) due by Friday,August 23rd. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

[feiskyer]

docs are not required for this feature. However, we're working on the e2e tests.

[simplytunde]

Thanks @feiskyer

[feiskyer]

E2e tests are now added via a set of changes:

• https://github.com/kubernetes/cloud-provider-azure/issues/176
• https://github.com/kubernetes/cloud-provider-azure/pull/196
• https://github.com/kubernetes/test-infra/pull/13620

Documentation has been added to https://github.com/kubernetes/cloud-provider-azure/blob/master/docs/using-availability-zones.md.

So we are ok to close this now.

/close

[k8s-ci-robot]

@feiskyer: Closing this issue.

In response to this:

E2e tests are now added via a set of changes:

• https://github.com/kubernetes/cloud-provider-azure/issues/176
• https://github.com/kubernetes/cloud-provider-azure/pull/196
• https://github.com/kubernetes/test-infra/pull/13620

Documentation has been added to https://github.com/kubernetes/cloud-provider-azure/blob/master/docs/using-availability-zones.md.

So we are ok to close this now.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.