Skip to content

KEP-4205: updating the milestone for alpha to 1.30 #4454

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 3, 2024
Merged

KEP-4205: updating the milestone for alpha to 1.30 #4454

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions keps/sig-node/4205-psi-metric/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -421,7 +421,7 @@ well as the [existing list] of feature gates.
Any change of default behavior may be surprising to users or break existing
automations, so be extremely careful here.
-->
Not in Phase 1. Phase 2 is TBD in K8s 1.30.
Not in Phase 1. Phase 2 is TBD in K8s 1.31.

###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?

Expand Down Expand Up @@ -598,7 +598,7 @@ and creating new ones, as well as about cluster-level services (e.g. DNS):
- Impact of its outage on the feature:
- Impact of its degraded performance or high-error rates on the feature:
-->
Yes, it depends on runc version 1.2.0.
Yes, it depends on runc version 1.2.0. This KEP can be implemented only after runc 1.2.0 is released, which is estimated to be released in Q1 2024.

### Scalability

Expand Down
4 changes: 2 additions & 2 deletions keps/sig-node/4205-psi-metric/kep.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,11 @@ stage: alpha
# The most recent milestone for which work toward delivery of this KEP has been
# done. This can be the current (upcoming) milestone, if it is being actively
# worked on.
latest-milestone: "v1.29"
latest-milestone: "v1.30"

# The milestone at which this feature was, or is targeted to be, at each stage.
milestone:
alpha: "v1.29"
alpha: "v1.30"

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