Skip to content

Commit 8c4d319

Browse files
authored
Merge pull request #4459 from RaunakShah/3141-kep-4
KEP-3141: Graduate "Prevent unauthorised volume mode conversion" to Stable
2 parents 3b6832c + 42fe914 commit 8c4d319

File tree

3 files changed

+10
-4
lines changed

3 files changed

+10
-4
lines changed

keps/prod-readiness/sig-storage/3141.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,5 @@ alpha:
66
approver: "@deads2k"
77
beta:
88
approver: "@deads2k"
9+
stable:
10+
approver: "@deads2k"

keps/sig-storage/3141-prevent-volume-mode-conversion/README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@ Consider including folks who also work outside the SIG or subproject.
262262
## Design Details
263263

264264
A new out-of-tree flag named `PreventVolumeModeConversion` will be introduced on
265-
`external-snapshotter` and `external-provisioner`. Both of these components are
265+
`snapshot-controller` and `csi-provisioner`. Both of these components are
266266
out-of-tree so this proposal will not require any in-tree feature gates.
267267

268268
### Changes to VolumeSnapshotContent API
@@ -735,6 +735,10 @@ Major milestones might include:
735735
- when the KEP was retired or superseded
736736
-->
737737
738+
- 2023-02-06: KEP updated to mark transition to beta off-by-default
739+
- 2023-12-23: KEP updated to mark transition to beta on-by-default
740+
- 2024-01-24: KEP updated to mark transition to stable
741+
738742
## Drawbacks
739743
740744
<!--

keps/sig-storage/3141-prevent-volume-mode-conversion/kep.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,18 @@ approvers:
1717
- "@liggitt"
1818

1919
# The target maturity stage in the current dev cycle for this KEP.
20-
stage: beta
20+
stage: stable
2121

2222
# The most recent milestone for which work toward delivery of this KEP has been
2323
# done. This can be the current (upcoming) milestone, if it is being actively
2424
# worked on.
25-
latest-milestone: "v1.27"
25+
latest-milestone: "v1.30"
2626

2727
# The milestone at which this feature was, or is targeted to be, at each stage.
2828
milestone:
2929
alpha: "v1.24"
3030
beta: "v1.27"
31-
stable: "v1.28"
31+
stable: "v1.30"
3232

3333
# The following PRR answers are required at alpha release
3434
# List the feature gate name and the components for which it must be enabled

0 commit comments

Comments
 (0)