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

Provision volumes from cross-namespace snapshots #3294

Open
1 of 5 tasks
mkimuram opened this issue May 4, 2022 · 26 comments · Fixed by #3295
Open
1 of 5 tasks

Provision volumes from cross-namespace snapshots #3294

mkimuram opened this issue May 4, 2022 · 26 comments · Fixed by #3295
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lead-opted-in Denotes that an issue has been opted in to a release sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@mkimuram
Copy link
Contributor

mkimuram commented May 4, 2022

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@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 4, 2022
@xing-yang
Copy link
Contributor

xing-yang 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/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 23, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented May 30, 2022

Hello @mkimuram 👋, 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 alpha 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 open KEP PR #3295 for 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!

@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 30, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 11, 2022

Hello @mkimuram 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get the above criterias done before the upcoming enhancements freeze on Thursday, June 16, 2022 at 18:00 PM PT.

For note, the current status of the enhancement is at at-risk. Thank you!

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 21, 2022

Hello @mkimuram 👋, another check-in, as we approach the 1.25 enhancements freeze.

All required criteria are fulfilled by the open PR #3295.

We just now require merging it before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT, which is just over 3 days away from now.

For note, the current status of the enhancement is atat-risk. Thank you!

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 24, 2022

Hello, 1.25 Enhancements Lead here 👋. With Enhancements Freeze now in effect, this enhancement has not met the criteria for the freeze and has been removed from the milestone.

As a reminder, the criteria for enhancements freeze is:

  • KEP file using the latest template has been merged into the k/enhancements repo, with up to date latest milestone and stage
  • KEP status is marked as implementable
  • KEP has an 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.

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks!
/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Jun 24, 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 Jun 24, 2022
@xing-yang xing-yang added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 12, 2022
@xing-yang
Copy link
Contributor

xing-yang commented Sep 12, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Sep 12, 2022
@xing-yang xing-yang removed this from the v1.25 milestone Sep 12, 2022
@xing-yang
Copy link
Contributor

xing-yang commented Sep 12, 2022

/milestone v1.26

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 12, 2022
@xing-yang
Copy link
Contributor

xing-yang commented Sep 12, 2022

/assign @ttakahashi21

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 12, 2022

@xing-yang: GitHub didn't allow me to assign the following users: ttakahashi21.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @ttakahashi21

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.

@ttakahashi21 ttakahashi21 removed their assignment Sep 12, 2022
@ttakahashi21
Copy link
Contributor

ttakahashi21 commented Sep 12, 2022

/assign @ttakahashi21

@rhockenbury rhockenbury 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 Sep 20, 2022
@marosset
Copy link
Contributor

marosset commented Sep 20, 2022

Hello @Elbehery & @mkimuram 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

It looks like #3295 will address most of these issues.

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!

@msau42
Copy link
Member

msau42 commented Oct 6, 2022

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Oct 6, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Oct 6, 2022

@msau42: Reopened this issue.

In response to this:

/reopen

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.

@marosset
Copy link
Contributor

marosset commented Oct 6, 2022

With #3295 merged I'm updating the status of this enhancement to tracked for v1.26.
Thanks!

@ttakahashi21
Copy link
Contributor

ttakahashi21 commented Oct 19, 2022

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Oct 19, 2022

@ttakahashi21: Reiterating the mentions to trigger a notification:
@kubernetes/sig-storage-feature-requests

In response to this:

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

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.

@mickeyboxell
Copy link

mickeyboxell commented Oct 20, 2022

@mkimuram Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

@mkimuram
Copy link
Contributor Author

mkimuram commented Oct 24, 2022

@mkimuram Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

Docs are required. @ttakahashi21 or I will open the docs PRs described in the updated "Enhancement Description" above.

@marosset
Copy link
Contributor

marosset commented Oct 31, 2022

Hi @Elbehery & @mkimuram 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • 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.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

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

@mickeyboxell
Copy link

mickeyboxell commented Nov 2, 2022

Hi @mkimuram and @ttakahashi21 👋 Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time. It must be created by November 9. For more information, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

@marosset
Copy link
Contributor

marosset commented Nov 7, 2022

Hi @Elbehery & @mkimuram 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • 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.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

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

@mickeyboxell
Copy link

mickeyboxell commented Nov 8, 2022

Hey @mkimuram and @ttakahashi21, this is a reminder to open a PR against dev-1.26 branch in the k/website repo by November 9. This PR can be just a placeholder at this time.

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for code freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot 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 lead-opted-in Denotes that an issue has been opted in to a release labels Nov 9, 2022
@leonardpahlke
Copy link
Member

leonardpahlke commented Nov 10, 2022

exception request granted

Your updated deadline to make any changes is 18:00 PST Friday 11th November 2022

/milestone v1.26
/label tracked/yes
/label lead-opted-in
/remove-label tracked/no

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Nov 10, 2022
@k8s-ci-robot k8s-ci-robot added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Nov 10, 2022
@krol3
Copy link

krol3 commented Nov 28, 2022

Hi @mkimuram ! how are you? Here the doc Lead about 1.26. Can you help me with the doc-PR? I can only find the PR about the blog kubernetes/website#37628

cc: @reylejano @mickeyboxell

@leonardpahlke
Copy link
Member

leonardpahlke commented Nov 28, 2022

@krol3 kubernetes/website#37802

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. lead-opted-in Denotes that an issue has been opted in to a release sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Net New
Development

Successfully merging a pull request may close this issue.