search

kubernetes / kubernetes

Production-Grade Container Scheduling and Management
https://kubernetes.io
Apache License 2.0
109.67k stars 39.27k forks source link

[KMS] Strategy for storage migration #111925

Open aramase opened 2 years ago

aramase commented 2 years ago

Creating this umbrella issue to track how we handle storage migration for kms:

/sig auth /cc @enj /triage accepted

enj commented 2 years ago

/milestone v1.26

(We need to come up with some plan for this during the release, even if the actual implementation takes many releases)

r-erema commented 1 year ago

We need to come up with some plan

@enj Hi! May I look into the issue and try to provide a plan followed by implementation?

enj commented 1 year ago

We need to come up with some plan

@enj Hi! May I look into the issue and try to provide a plan followed by implementation?

No I am already working on it, just forgot to assign it.

/assign

HeshamAboElMagd commented 1 year ago

Hello @enj . bug triage team here, just wanted to touch base with you for updates on this ticket. Thanks!

enj commented 1 year ago

Hello @enj . bug triage team here, just wanted to touch base with you for updates on this ticket. Thanks!

Work is ongoing as part of https://github.com/kubernetes/enhancements/issues/3299

enj commented 1 year ago

/milestone v1.27

k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle stale

aramase commented 1 year ago

/remove-lifecycle stale

furkatgofurov7 commented 1 year ago

Hi @aramase! Bug triage shadow for release cycle v1.27 here.

This issue hasn't been updated for some time (excluding lifecycle stale removal), are you still expecting it to be completed for 1.27?

enj commented 1 year ago

@furkatgofurov7 this is not targeting 1.27

/milestone v1.28

hailkomputer commented 1 year ago

Hello @enj, v1.28 Bug Triage Shadow here checking in. It is still early in the release cycle, but do you know if this is still on track for the 1.28 release?

hailkomputer commented 1 year ago

Hello! Bug triage team shadow here. I want to check the status. The code freeze is starting 01:00 UTC Wednesday 19th July 2023 / 18:00 PDT Tuesday 18th July 2023 (about three weeks from now), and while there is still plenty of time, we want to ensure that each PR has a chance to be merged on time.

As the issue is tagged for 1.28, is it still planned for this release?

hailkomputer commented 1 year ago

Hi! Bug triage team shadow here.

We are currently in Week 9 of the v1.28 release cycle, and the code freeze is happening next week (Week 10) at 01:00 UTC Wednesday 19th July 2023 / 18:00 PDT Tuesday 18th July 2023

Please ensure all necessary contributions are made before the deadline if the Issue still targets v1.28.

Let me know if you need any assistance.

enj commented 1 year ago

/milestone v1.29

k8s-ci-robot commented 1 year ago

@enj: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/kubernetes/issues/111925#issuecomment-1642072842): >/milestone v1.29 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
enj commented 1 year ago

/milestone next-candidate

enj commented 1 year ago

/milestone v1.29

hailkomputer commented 10 months ago

Hello @enj , bug triage team lead here. I want to check the status. The code freeze is starting 01:00 UTC Wednesday 1st November 2023 / 18:00 PDT Tuesday 31st October 2023 (about two weeks from now), and while there is still plenty of time, we want to ensure that each PR has a chance to be merged and issue’s are addressed on time. As the issue is tagged for 1.29, is it still planned for this release?

hailkomputer commented 10 months ago

Hello @enj and @aramase, bug triage team lead here again. I want to echo that the code freeze is starting 01:00 UTC Wednesday 1st November 2023 / 18:00 PDT Tuesday 31st October 2023 (next week), and we want to ensure that each PR has a chance to be merged and issues can be addressed. Is this issue still targeting the 1.29 release?

dims commented 9 months ago

/milestone v1.30

kicking the can, we are way past code freeze

MaryamTavakkoli commented 7 months ago

Hello! Release Signal shadow here. This issue has not been updated for a long time, so I'd like to check what's the status. The code freeze is starting 02:00 UTC Wednesday 6th March 2024 / 18:00 PDT Tuesday 5th March 2024 (less than a month from now), and while there is still plenty of time, we want to ensure that each PR has a chance to be merged on time.

As this issue is tagged for 1.30, is it still planned for this release?

MaryamTavakkoli commented 6 months ago

Hello! Release Signal shadow here. This issue has not been updated for a long time, so I'd like to check what's the status. The code freeze is starting 02:00 UTC Wednesday 6th March 2024 / 18:00 PDT Tuesday 5th March 2024 in a week, and we want to ensure that each PR has a chance to be merged on time.

As this issue is tagged for 1.30, is it still planned for this release?

MaryamTavakkoli commented 6 months ago

/milestone clear

k8s-ci-robot commented 6 months ago

@MaryamTavakkoli: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/kubernetes/kubernetes/issues/111925#issuecomment-1981408226): >/milestone clear Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Vyom-Yadav commented 6 months ago

We have passed the code freeze stage.

/milestone clear

@dims Should this be added to v1.31?

Vyom-Yadav commented 6 months ago

/milestone v1.31

To have better visibility, I'll move this to the next release.

Vyom-Yadav commented 2 months ago

Hello @enj! This issue has not been updated for a long time, so I'd like to check what's the status. The code freeze is starting 02:00 UTC Wednesday 10th July 2024 (about 4 weeks from now), and while there is still plenty of time, we want to ensure that each PR has a chance to be merged on time.

As the issue is tagged for 1.31, is it still planned for this release?

Vyom-Yadav commented 1 month ago

Hello @enj,

This issue hasn't been updated in a while. What's the current status?

Reminder: Code freeze starts 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024 (about 1 week from now). Please make sure the related PR has both lgtm and approved labels before the code freeze.

enj commented 1 month ago

/milestone v1.33

k8s-ci-robot commented 1 month ago

@enj: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate, v1.26, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/kubernetes/issues/111925#issuecomment-2246443793): >/milestone v1.33 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
enj commented 1 month ago

/milestone v1.32