Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS EBS topology support #567

Closed
msau42 opened this issue May 8, 2018 · 25 comments
Closed

AWS EBS topology support #567

msau42 opened this issue May 8, 2018 · 25 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status

Comments

@msau42
Copy link
Member

msau42 commented May 8, 2018

One-line feature description (can be used as a release note): AWS EBS topology support
Primary contact (assignee): @ddebroy
Responsible SIGs: sig-storage
Design proposal link (community repo):
Link to e2e and/or unit tests:
Reviewer(s): @gnufied @jsafrane
Approver (likely from SIG/area to which feature belongs): @gnufied @jsafrane
Feature target (which target equals to which milestone):
Alpha release target (x.y) 1.11
Beta release target (x.y) 1.12
Stable release target (x.y) 1.13

@msau42
Copy link
Member Author

msau42 commented May 8, 2018

@kubernetes/sig-storage-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. kind/feature Categorizes issue or PR as related to a new feature. labels May 8, 2018
@justaugustus
Copy link
Member

justaugustus commented Jul 18, 2018

@msau42 -- I'm assigning this to you, but if there's someone more appropriate, feel free to reassign.
/assign @msau42
/cc @justaugustus @kacole2 @robertsandoval @rajendar38

@msau42
Copy link
Member Author

msau42 commented Jul 18, 2018

/assign @ddebroy

@k8s-ci-robot
Copy link
Contributor

@msau42: GitHub didn't allow me to assign the following users: ddebroy.

Note that only kubernetes members and repo collaborators can be assigned.

In response to this:

/assign @ddebroy

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.

@msau42
Copy link
Member Author

msau42 commented Jul 18, 2018

@ddebroy is working on this, but I can't assign
/assign @jsafrane
as placeholder
/unassign

@justaugustus
Copy link
Member

@jsafrane @msau42 --

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!

@saad-ali saad-ali added this to the v1.12 milestone Jul 27, 2018
@saad-ali saad-ali added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Jul 27, 2018
@justaugustus justaugustus added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 29, 2018
@zparnold
Copy link
Member

Hey there! @msau42 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
Copy link
Member Author

msau42 commented Aug 20, 2018

Doc placeholder: kubernetes/website#9939

@zparnold
Copy link
Member

Thanks!

@zparnold
Copy link
Member

zparnold commented Aug 20, 2018 via email

@ddebroy
Copy link
Member

ddebroy commented Aug 30, 2018

/assign @ddebroy

@ddebroy
Copy link
Member

ddebroy commented Aug 30, 2018

Addressed by kubernetes/kubernetes#65730

@justaugustus
Copy link
Member

@ddebroy @msau42 @jsafrane --
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

@msau42
Copy link
Member Author

msau42 commented Sep 5, 2018

yes docs in progress

@justaugustus
Copy link
Member

Thanks for the update!

@justaugustus
Copy link
Member

@msau42 -- what's the status on this? Are we ready to merge the docs PR and has associated code been merged?

@msau42
Copy link
Member Author

msau42 commented Sep 11, 2018

Code is in and docs PR is under review kubernetes/website#9939

@justaugustus
Copy link
Member

thanks @msau42!

@ameukam
Copy link
Member

ameukam commented Oct 5, 2018

Hi folks,
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 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

@msau42
Copy link
Member Author

msau42 commented Oct 5, 2018

Yes, we plan to move this to GA in 1.13.

@saad-ali saad-ali modified the milestones: v1.12, v1.13 Oct 5, 2018
@AishSundar
Copy link

@msau42 is there a list of pending PRs or issues (code, tests and docs)you are tracking for this feature to go to GA? how complete is this feature?

@msau42
Copy link
Member Author

msau42 commented Oct 17, 2018

This feature is a subset of #490, but doesn't have any separate tasks that aren't already covered. Would it be easier to close this and just track #490?

@AishSundar
Copy link

yes please if there is no tasks specific to this one at all. @kacole2 as FYI

@kacole2
Copy link

kacole2 commented Oct 18, 2018

/close
/milestone clear

@k8s-ci-robot
Copy link
Contributor

@kacole2: Closing this issue.

In response to this:

/close
/milestone clear

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.

@k8s-ci-robot k8s-ci-robot removed this from the v1.13 milestone Oct 18, 2018
@kacole2 kacole2 removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
None yet
Development

No branches or pull requests

10 participants