Open aramase opened 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)
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?
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
Hello @enj . bug triage team here, just wanted to touch base with you for updates on this ticket. Thanks!
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
/milestone v1.27
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
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?
@furkatgofurov7 this is not targeting 1.27
/milestone v1.28
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?
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?
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.
/milestone v1.29
@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.
/milestone next-candidate
/milestone v1.29
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?
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?
/milestone v1.30
kicking the can, we are way past code freeze
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?
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?
/milestone clear
@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.
We have passed the code freeze stage.
/milestone clear
@dims Should this be added to v1.31
?
/milestone v1.31
To have better visibility, I'll move this to the next release.
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?
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.
/milestone v1.33
@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.
/milestone v1.32
Creating this umbrella issue to track how we handle storage migration for kms:
currentKeyID
v1beta1
to enable migration fromAES-CBC
toAES-GCM
https://github.com/kubernetes/kubernetes/blob/d581cc90adba6c84919738841fe3e07302d53e33/staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig/config.go#L490-L492/sig auth /cc @enj /triage accepted