Re: [kubernetes/enhancements] Raw block device using persistent volume source (#351)

[Tim Fogarty]

@wongma7 I rebased this docs PR to dev-1.13 and reopened it for you. Are you okay to use that PR for the docs for this? kubernetes/website#10100

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Matthew Wong]

@tfogo yes, thanks! will be working on it shortly, k/k pr is awaiting approval

[Claire Laurence]

Hi @childsb @wongma7 -I'm an enhancements shadow checking in on this issue - sounds like progress is being made - as an FYI code slush is 11/9 and Code freeze is 11/15 - any concerns about making those dates

[Kendrick Coleman]

@wongma7 there hasn't been any progress on kubernetes/kubernetes#65829 for about 7 days. Do we feel confident it's going to merge by tomorrow since that's the beginning of code slush?

[Matthew Wong]

@kacole2 @claurence yes, just needs final review from approvers. brought it up in meeting today and they will be looking at it.

[Aish Sundar]

@wongma7 I see the PR kubernetes/kubernetes#65829 is actively under review. Please let us know if there is a potential of this slipping 5pm Code freeze tomorrow. Thanks

[Niko Pen]

@AishSundar It likely will slip to next week as it requires lots of approvals. Tests went green and there are a few last items.

[Michelle Au]

I think this can still make it in today if kubernetes/kubernetes#71100 merges soon

[Aish Sundar]

This seems super tight to me. Will watch both PRs today

[Claire Laurence]

@erinboyd, @screeley44, @mtanino Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. It looks like this was targeted to go stable in 1.13, is there work open for 1.14 that needs to be done or should this issue be closed?

[Michelle Au]

The plan is to remain in beta for 1.14.

[Jim Angel]

Hey @erinboyd @childsb @msau42 👋 I'm the v1.14 docs release lead.

Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. 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!

[Michelle Au]

This feature is remaining beta in 1.14. There are no plans to update docs.

[Aaron Crickenberger]

/milestone clear
@msau42 if this landed as beta in v1.13, and is staying beta in v1.14, I'm not sure we as the release team need to be tracking it, please add back if I'm wrong

[Michelle Au]

correct

[Kendrick Coleman]

Hello @msau42 @erinboyd , 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. This will also require a KEP to be included.

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

[Michelle Au]

This is remaining beta in 1.15

[Kendrick Coleman]

Hi @msau42 , I'm the 1.16 Enhancement Lead/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.

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

As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

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

Thank you.

[Michelle Au]

This feature is remaining beta for 1.16

[Kristin Martin]

Hello @msau42, 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to stable in 1.17?


Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

The current release schedule is

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

A Kubernetes Enhancement Proposal (KEP) must meet the following criteria before Enhancement Freeze to be accepted into the release

• PR is merged in
• In an implementable state
• Include test plan and graduation criteria
• All relevant k/k PRs should be listed in this issue

Thank you.

[Jan Šafránek]

We're aiming at GA in 1.17. Created KEP for the feature: #1288 (it was designed before KEP was a thing).
Remaining work is tracked here: https://github.com/orgs/kubernetes-csi/projects/4

[Kristin Martin]

Thanks @jsafrane

—
You are receiving this because you are on a team that was mentioned.

Reply to this email directly, view it on GitHub, or unsubscribe.

[Kristin Martin]

/milestone v1.17

[Kristin Martin]

/stage stable

[Kristin Martin]

One more thing, @jsafrane -- We're only 5 days away from the Enhancements Freeze (Tuesday, October 15, EOD PST). Another friendly reminder that to be able to graduate this in the 1.17 release, KEP must have graduation criteria defined, in an implementable state, and merged in. Thank you!

[Irvi Aini]

Hello @msau42 I'm one of the v1.17 docs shadows.
Does this enhancement for (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[Irvi Aini]

@msau42

Since we're approaching Docs placeholder PR deadline on Nov 8th. Please try to get one in against k/website dev-1.17 branch.

[Michelle Au]

/assign @jsafrane

[Jan Šafránek]

Doc changes: kubernetes/website#17399

[Jan Šafránek]

Test report with today's sources on GCE

I performed tests required by KEP:

• Test that the pods are moved to another nodes and data is retained when the node is drained.
  • All 37 pods of 37 Deployments were killed on the original node and moved to other nodes, with their content preserved. Symlinks on the original node were cleaned.
• Test that the data is retained when kubelet restarts while the pods are running.
  • No issue at all.
• Test that the data is retained when the node reboots. For pods that were moved to another nodes during the outage, test that the newly started node cleaned up their devices.
  • The pods entered Error state and were restarted after reboot. All pods were restarted on the same node as before. Kubelet was able to find all devices and run the pods after reboot.

Test setup:

• 3 node cluster, each node could handle 37 pods (otherwise dd and md5sum was terribly slow). It's not much, I could bump nr. of CPUs if required.
• GCE PD was used.
• Each volume pre-filled with dd if=/dev/urandom and storing its md5sum.
• Each pod did md5sum /dev/test-disk every now and then, e.g. during node drain, reboot and so on to simulate some load (read-only, but at least something...)

[Kristin Martin]

Hi @msau42 and @jsafrane

I am one of the Enhancements Shadows for the 1.17 Release Team. We are very near to Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. I don't see any kubernetes/kubernetes PRs related to this enhancement, can you please link them here?

Thank you in advance 😄

[Jan Šafránek]

This PR is needed: kubernetes/kubernetes#84784

[Kristin Martin]

Hi @jsafrane and @msau42 -- tomorrow is code freeze for the 1.17 release cycle. It looks like the k/k PRs have not yet been merged. We're flagging as At Risk in the 1.17 Enhancement Tracking Sheet.

Do you think they will be merged by the EoD of the 14th (Thursday)? After that point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

Thank you!

[Saad Ali]

We are removing this feature from 1.17 and pushing it to 1.18

We want to align moving both this (in-tree) and CSI raw block (#565) to GA at the same time. If CSI raw block GA slips past 1.18, we can reconsider moving this to GA independently.

/milestone v1.18

[Kristin Martin]

@saad-ali Thank you for the update, we will remove from the tracking sheet!

[Jeremy Rickard]

Hello @saad-ali

Are you still planning on graduating this with #565? For your awareness, the enhancement freeze will be January 28th and the code freeze will be March 5th!

[Michelle Au]

/assign @jsafrane
who is planning to work on this for 1.18

[Jeremy Rickard]

@jsafrane @msau42 I assume the comment above means we should we track this for 1.18? Thanks!

[Jeremy Rickard]

@jsafrane @msau42 we're about a week away from Enhancement Freeze now. Do you plan on including any of this in 1.18? We're currently not tracking this or #565, and we'll need to do that prior to the enhancement freeze if you'd like to graduate this in 1.18!

[Michelle Au]

Yes this should be tracked along with #565

[Seth McCombs]

Hey @jsafrane @msau42 -

Seth here, Docs shadow on the 1.18 release team.

Does this enhancement work planned for 1.18 require any new docs or modifications to existing docs?

If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)

If doc updates are required, reminder that the placeholder PRs against k/website (branch dev-1.18) are due by Friday, Feb 28th.

Let me know if you have any questions!

—

[Jeremy Rickard]

Hello @msau42 kube-proxy-9t6v6,

Just a friendly reminder that code freeze for 1.18 is March 05, 2020.

As we track toward code freeze, please list out/link to any PRs you are working on toward graduating this enhancement!

[Jeremy Rickard]

Hello @msau42 @jsafrane

We're getting close to code freeze next week, 05 March 2020

Can you please share any PRs that are in flight for this so that we can properly track the issue? This includes both k/k PRs and placeholder PRs against k/website (branch dev-1.18), which are due by Friday, Feb 28th.

[Jan Šafránek]

Doc PR: kubernetes/website#19338

[Jan Šafránek]

We track all issues/PR for GA in this board: https://github.com/orgs/kubernetes-csi/projects/4

[Mirek Sedzinski]

Hey there @erinboyd, @screeley44 , @mtanino -- 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
• Thursday, August 20: Week 19 - Release Retrospective

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!

[Nabarun Pal]

/close

(closing this since the KEP has been implemented)

[Kubernetes Prow Robot]

Closed #351.

[Kubernetes Prow Robot]

@palnabarun: Closing this issue.

In response to this:

/close

(closing this since the KEP has been implemented)

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.

[Mirek Sedzinski]

/milestone clear

[Nabarun Pal]

/milestone v1.18

(since the enhancement graduated to Stable in 1.18 release cycle)