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.

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

Update KEP 3157 (watch-list) for milestone 1.32 #4836

Merged
merged 1 commit into from
Sep 9, 2024
+3 −2
Merged

Update KEP 3157 (watch-list) for milestone 1.32 #4836

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
1 change: 1 addition & 0 deletions keps/sig-api-machinery/3157-watch-list/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -675,6 +675,7 @@ We expect no non-infra related flakes in the last month as a GA graduation crite
with data obtained through a standard list request. The detector will be added to the reflector
and activated when an environment variable is set. The environment variable will be set for all jobs run in the Kube CI.
- Update the client-go generated List function to watchList data when the feature gate has been enabled and the ListOptions are satisfied.
This change must be applied to the typed, dynamic and metadata clients.
- Implement a mechanism for automatically detecting etcd configuration
Whether it is safe to use the RequestWatchProgress API call
or if the experimental-watch-progress-notify-interval flag has been set.
Expand Down
4 changes: 2 additions & 2 deletions keps/sig-api-machinery/3157-watch-list/kep.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,12 @@ stage: beta
# 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.31"
latest-milestone: "v1.32"

# The milestone at which this feature was, or is targeted to be, at each stage.
milestone:
alpha: "v1.27"
beta: "v1.31"
beta: "v1.32"

# 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