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

CSI Inline Volume Support #596

Closed
saad-ali opened this issue Jul 28, 2018 · 105 comments
Closed

CSI Inline Volume Support #596

saad-ali opened this issue Jul 28, 2018 · 105 comments
Assignees
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API 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/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

@saad-ali
Copy link
Member

saad-ali commented Jul 28, 2018

Feature Description

@saad-ali saad-ali added this to the v1.12 milestone Jul 28, 2018
@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 Jul 28, 2018
@justaugustus
Copy link
Member

justaugustus commented Jul 28, 2018

Thanks for the update! This has been added to the 1.12 Tracking sheet.

/assign @jsafrane
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jul 28, 2018
@justaugustus justaugustus added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 28, 2018
@zparnold
Copy link
Member

zparnold commented Aug 20, 2018

Hey there! @saad-ali 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?

@justaugustus
Copy link
Member

justaugustus commented Sep 5, 2018

@jsafrane @vladimirvivien --
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

@saad-ali
Copy link
Member Author

saad-ali commented Sep 6, 2018

This PR (kubernetes/kubernetes#67452) did not make it to 1.12. Moving to next milestone

@saad-ali saad-ali modified the milestones: v1.12, v1.13 Sep 6, 2018
@justaugustus
Copy link
Member

justaugustus commented Sep 6, 2018

Thanks for the update!

@justaugustus justaugustus 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 6, 2018
@kacole2 kacole2 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 Oct 8, 2018
@vladimirvivien
Copy link
Member

vladimirvivien commented Oct 9, 2018

/assign vladimirvivien

@AishSundar
Copy link

AishSundar commented Oct 17, 2018

@saad-ali @vladimirvivien how confident are we about this going Alpha in 1.13? Is there a list of pending PRs or issues we are tracking for this work?

@kacole2
Copy link
Member

kacole2 commented Oct 22, 2018

@vladimirvivien there hasn't been any communication on this issue but from the looks of kubernetes/kubernetes#68232 there is activity happening so this is going to continue to be tracked for v1.13 milestone.

@tfogo
Copy link
Member

tfogo commented Nov 1, 2018

Hi @vladimirvivien @jsafrane @saad-ali, I'm the docs wrangler for the 1.13 release. Could you please open a placeholder PR for the docs for this enhancement against the dev-1.13 branch of k/website and send me a link? If you already have a docs PR open, or if this doesn't require docs in k/website, please let me know.

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 you have any questions about any of this, I'm happy to help. You can also message me on slack (I'm tfogo there too).

Thanks!

@claurence
Copy link

claurence commented Nov 7, 2018

Hi @vladimirvivien I'm an enhancements shadow checking in on how this issue is tracking - looks like lots of activity in the K/K PR. Code slush is on 11/9 and code freeze is coming up on 11/15 are you confident this issue will make those dates?

@vladimirvivien
Copy link
Member

vladimirvivien commented Nov 9, 2018

Doc - kubernetes/website#10934

@AishSundar
Copy link

AishSundar commented Nov 9, 2018

@tfogo for docs PR

@AishSundar
Copy link

AishSundar commented Nov 12, 2018

@vladimirvivien @saad-ali could you plz provide the latest update on this enhancement and status for 1.13 please. Is kubernetes/kubernetes#68232 is the only pending PR (code snd test).

@kacole2
Copy link
Member

kacole2 commented Nov 14, 2018

/milestone 1.14

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented May 30, 2022

Hello @dobsonj @saad-ali 👋, 1.25 Enhancements team here.

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

For note, This enhancement is targeting for stage stable for 1.25 (correct me, if otherwise)

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 would need to update the following:

Open PR #3368 addresses the ^

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!

@dobsonj
Copy link
Member

dobsonj commented Jun 10, 2022

Hi @Priyankasaggu11929 , I opened a PR to update the KEP template and milestones, including the new test plan section:
#3368

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 21, 2022

With KEP PR #3368 merged, the PR is ready for the enhancements freeze. 🚀

For note, the status is not tracked in the 1.25 Enhancements Tracking spreadsheet. Thank you!

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jul 21, 2022

Hello @dobsonj 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

Please verify, if there are any additional k/k PRs besides the ones listed above.

Please plan to get the open k/k merged by the code freeze deadline. The status of the enhancement is currently marked as at-risk.

Please also update the issue description with the relevant links for tracking purpose. Thank you so much!

@krol3
Copy link

krol3 commented Jul 27, 2022

Hello @dobsonj 👋, 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!

@AnaMMedina21
Copy link

AnaMMedina21 commented Jul 27, 2022

Hi @dobsonj 👋🏽

I’m one of the 1.25 Release Comms Shadow, Thanks for submitting this KEP for a Feature Blog. We have the code freeze upcoming and need to have a placeholder PR up already. Once you have it up, leave a comment on here (or slack me, and I will add it to the tracking sheet)

Let me know if you have any questions or if I can assist in any way :)

@dobsonj
Copy link
Member

dobsonj commented Jul 28, 2022

@krol3 @AnaMMedina21 placeholder PR's opened:
k/website: kubernetes/website#35510
csi docs: kubernetes-csi/docs#520
blog: kubernetes/website#35511

@AnaMMedina21
Copy link

AnaMMedina21 commented Jul 28, 2022

@dobsonj - Thank you! Just added it to our tracking sheet

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 1, 2022

Hello @dobsonj 👋

Just a gentle reminder from the enhancement team as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022 (which is almost 2 days from now).

Please plan to have the open k/k PR merged before then.

The status of this enhancement is currently marked as at risk

Thank you.

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 3, 2022

Hello 👋, 1.25 Enhancements Lead here.

Unfortunately, this enhancement did not meet the code freeze criteria because there are still unmerged k/k code PRs.

If you still wish to progress this enhancement in v1.25, please file an exception request. Thank you so much!

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Aug 3, 2022
@Priyankasaggu11929 Priyankasaggu11929 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 Aug 3, 2022
@dobsonj
Copy link
Member

dobsonj commented Aug 5, 2022

Hello @Priyankasaggu11929 , the exception request was approved today and the PR merged:
kubernetes/kubernetes#111258 (comment)
Can you please add the 1.25 milestone back for this enhancement?

@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 Aug 6, 2022
@Priyankasaggu11929 Priyankasaggu11929 added this to the v1.25 milestone Aug 6, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 6, 2022

done. 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
@dobsonj
Copy link
Member

dobsonj commented Nov 10, 2022

This enhancement is complete, closing it out.
To recap: it graduated to GA in 1.25, I marked it as implemented in #3445 and promoted the conformance tests in kubernetes/kubernetes#111724
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 10, 2022

@dobsonj: Closing this issue.

In response to this:

This enhancement is complete, closing it out.
To recap: it graduated to GA in 1.25, I marked it as implemented in #3445 and promoted the conformance tests in kubernetes/kubernetes#111724
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API 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/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
None yet
Development

No branches or pull requests