/sig storage

/kind feature

/assign @xing-yang

/assign @jingxu97

/milestone v1.15
/stage alpha

@jingxu97 and @xing-yang, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be merged and in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

@craiglpeters We are trying to get the KEP merged by 4/30.

Hey @jingxu97 , @xing-yang I'm the v1.15 docs shadow.

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.15) due by Friday, May 31st. 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!

@christianh814 Sure, I'll submit a placeholder PR soon. Thanks!

Hi @christianh814, a placeholder doc PR is submitted: kubernetes/website#14560

Hey there @xing-yang . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

Hi @mrbobbytables The code for ExecutionHook will not be in-tree so it does not have to be merged by May 30th. Thanks!

@xing-yang Would you mind linking to the PRs even if its not in-tree? It may not need to be in by the 30th, but they're something that should be tracked for the Enhancement.

Thanks!

@mrbobbytables, right now the code is still in my private repo here: https://github.com/xing-yang/execution-hook. We need to create a new repo under kubernetes-sigs. We have not finalized on a repo name. I opened an issue to track this and we need to get the repo created as soon as possible: kubernetes-csi/external-snapshotter#125

Great, thank you for letting us know! :)

Since development work for ExecutionHook is out-of-tree, we don't need to create a doc in-tree. So I just closed kubernetes/website#14560.

Hey @xing-yang,

In order to make it back into the 1.18 release, you need to file an exception request TODAY. Friendly reminder: the instructions are here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

cc: @alejandrox1 @mrbobbytables @onlydole

Hi @jeremyrickard, there were some comments came up during the code review. It means we'll have to have a design discussion to decide which direction to go. So we won't add this back to 1.18. Thanks!

Thank you, @xing-yang!

@xing-yang Do we have a sync up call scheduled for driving this forward ? if yes, I would like to contribute to this through the same.

@humblec we don't have a call scheduled yet. I'm working on a proposal to address the review comments but it is not ready yet. Will keep you updated.

By the way, if you are interested in helping with moving the volume snapshot feature to GA, this ExecutionHook feature is not required for that.

@humblec and @ashish-amarnath, I added ExecutionHook to tomorrow's Data Protection WG agenda to discuss: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#

@humblec and @ashish-amarnath, I added ExecutionHook to tomorrow's Data Protection WG agenda to discuss: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#

Thanks @xing-yang ! will catch up on this.

/assign ashish-amarnath

Hi @xing-yang @humblec @ashish-amarnath -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate 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

@palnabarun We actually need to do some re-design on this. So we won't track this for 1.19 yet. Thanks!

Thank you @xing-yang for the updates. I will update the tracking sheet accordingly. 👍

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

/remove-lifecycle stale

Hi again @xing-yang 😄

Any plans for this in 1.20?

Thanks!
Kirsten

Hi @kikisdeliveryservice,

The plan is to go with a different approach as described here: #1977. If that goes through, we won't need this one any more.

Thanks!
Xing

Makes sense to me!

Just a ping that if you intend to use this one in 1.20, it would need test plans added by Enhancements Freeze October 6th.

Seems like 1977 is under heavy discussion though, but if you do end up wanting to move forward with this one, let me know.

Thanks @kikisdeliveryservice for the reminder! I did submit a PR for adding test plans a while ago but there's no plan for this in 1.20 so that PR won't be reviewed for now.

@xing-yang ahh good to know, just wanted to double check 😄

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

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@fejta-bot: Closing this issue.