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 in-tree to CSI driver migration #1487

Open
2 tasks
davidz627 opened this issue Jan 21, 2020 · 49 comments
Open
2 tasks

AWS EBS in-tree to CSI driver migration #1487

davidz627 opened this issue Jan 21, 2020 · 49 comments
Assignees
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Milestone

Comments

@davidz627
Copy link
Contributor

davidz627 commented Jan 21, 2020

Enhancement Description

Parent enhancement: #625
Public Migration testing CI: LINK

TODO

  • Replace design/KEP with specific one if needed
  • Link public migration testing CI
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 21, 2020
@davidz627
Copy link
Contributor Author

davidz627 commented Jan 21, 2020

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 21, 2020
@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 23, 2020

Hey @davidz627 @leakingtapan, just to confirm you are not targeting v1.18 for this, correct?

@leakingtapan
Copy link
Contributor

leakingtapan commented Jan 23, 2020

Nope. It’s for 1.19

@jeremyrickard jeremyrickard added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 29, 2020
@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 29, 2020

/milestone v1.19

@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Jan 29, 2020
@fejta-bot
Copy link

fejta-bot commented Apr 28, 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2020
@palnabarun
Copy link
Member

palnabarun commented Apr 28, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2020
@harshanarayana
Copy link

harshanarayana commented Apr 30, 2020

Hey there @davidz627 / @jsafrane -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

  1. The KEP PR must be merged in an implementable state
  2. The KEP must have test plans
  3. The KEP must have graduation criteria.

The current release schedule is:

  • Monday, April 13: Week 1 - Release cycle begins
  • Tuesday, May 19: Week 6 - Enhancements Freeze
  • Thursday, June 25: Week 11 - Code Freeze
  • Thursday, July 9: Week 14 - Docs must be completed and reviewed
  • Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

@harshanarayana
Copy link

harshanarayana commented May 2, 2020

Hey @jsafrane / @davidz627, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

@harshanarayana
Copy link

harshanarayana commented May 9, 2020

Hey @davidz627 / @jsafrane, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

@harshanarayana
Copy link

harshanarayana commented May 14, 2020

Hey @jsafrane / @davidz627, any plans for the Enhancements to be included in v1.19? Please let me know so that I can update the tracking sheet to show the inclusion state.

Enhancements freeze is on May 19

Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template.
Please take this opportunity to reformat your KEP and also answer the questions added to the template in that PR.

Thanks,
🖖

@jsafrane
Copy link
Member

jsafrane commented May 14, 2020

No, we're going to skip GA in 1.19.

@leakingtapan
Copy link
Contributor

leakingtapan commented May 15, 2020

Skipping 1.19 sounds reasonable to me

@harshanarayana
Copy link

harshanarayana commented May 18, 2020

Hey @jsafrane @leakingtapan Thanks for the confirmation. I've updated the trackers accordingly.

@harshanarayana harshanarayana removed this from the v1.19 milestone May 18, 2020
@fejta-bot
Copy link

fejta-bot commented Aug 16, 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 16, 2020
@george-angel
Copy link

george-angel commented Aug 17, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 17, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 13, 2020

Hi @jsafrane

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

@kikisdeliveryservice kikisdeliveryservice added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Sep 13, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 24, 2020

No, we're going to skip GA in 1.19.

Hi @jsafrane @leakingtapan

I'm a bit confused with the state of this KEP. Can you please update with the status? Should it be marked implemented and the issue closed? The linked KEP doesn't indicate that it was finished and there are no PRs linked to this issue.

Enhancements Freeze is October 6th, if we could sort this out soon, that would be great.

As a note, the format of KEPs has changed as mentioned above. If you could please update and include the missing sections noted above that would be great. See for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Best,
Kirsten

@msau42
Copy link
Member

msau42 commented Oct 2, 2020

Hi, this is the kep: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20190129-csi-migration.md

This feature is still beta, and we don't plan to move it to GA in 1.20

@wongma7
Copy link
Contributor

wongma7 commented Feb 4, 2022

Intend now to go GA in 1.25 instead of 1.24: #3213. THX

@gracenng gracenng added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Feb 4, 2022
@gracenng
Copy link
Member

gracenng commented Feb 4, 2022

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.24 milestone Feb 4, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented May 5, 2022

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 5, 2022
@george-angel
Copy link

george-angel commented May 6, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2022
@jsafrane
Copy link
Member

jsafrane commented May 13, 2022

/milestone 1.25

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented May 13, 2022

@jsafrane: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.25

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.

@jsafrane
Copy link
Member

jsafrane commented May 13, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone May 13, 2022
@xing-yang xing-yang added the stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status label May 23, 2022
@Priyankasaggu11929 Priyankasaggu11929 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jun 3, 2022
@rhockenbury
Copy link

rhockenbury commented Jun 4, 2022

👋 Hello @leakingtapan,

1.25 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we need to update the following:

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@rhockenbury
Copy link

rhockenbury commented Jun 9, 2022

Hello @leakingtapan @wongma7 @jsafrane - Enhancements freeze is one week away. Please be sure to complete all requirements (noted in my comment above) before enhancements freeze to be included in v1.25.

@rhockenbury
Copy link

rhockenbury commented Jun 20, 2022

With #3411 merged, I am marking this as tracked for the v1.25 cycle. Thanks!

@krol3
Copy link

krol3 commented Jul 6, 2022

Hello @wongma7 👋, 1.25 Release Docs Shadow here.
This enhancement is marked as ‘Needs Docs’ for 1.25 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by August 4.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. 


Thank you!

@rhockenbury
Copy link

rhockenbury commented Jul 21, 2022

👋 Hey @leakingtapan,

Enhancements team checking in as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed by code freeze:
[ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
[ ] All PRs are fully merged by the code freeze deadline.

I didn't see any PRs (open or merged) in k/k for the graduation for this enhancement to stable. Let me know if I missed it.

As always, we are here to help should questions come up. Thanks!!

@rhockenbury
Copy link

rhockenbury commented Jul 27, 2022

Gentle reminder that we are about a week from code freeze, and all k/k PRs need to be merged before code freeze for this enhancement to be included in v1.25. Please let me know if there are any PRs we should be tracking.

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 2, 2022

With the code k/k PR kubernetes/kubernetes#111479 merged now, this enhancement is ready for 1.25 code freeze.

The status is now marked as tracked. Thank you!

@rhockenbury rhockenbury added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
No open projects
Development

No branches or pull requests