-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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.
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
Track stabilization of --experimental-watch-progress-notify-interval flag #13779
Comments
Adding some reference from kubernetes. Looks like GCE defaults to
ref. https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/config-default.sh#L524-L525
Please assign to me and I will take a look at this feature. Thanks! |
This is now a default in |
The flag |
…flag for etcd The experimental-watch-progress-notify-interval flag specifies an interval at which etcd sends data to the kube-api server. It is used by the WatchBookmark feature ( kube-apiserver) which is GA since 1.17. It will also be used by a new WatchList and WatchListClient features which are targeted to Beta in this release (1.30) All GCE tests set the flag as well. Given the above, a default installation must pass the flag required by the kube-apiserver to etcd. Otherwise, some features will not work. etcd-io/etcd#13779 tracks stabilization of the flag in etcd.
…flag for etcd The experimental-watch-progress-notify-interval flag specifies an interval at which etcd sends data to the kube-api server. It is used by the WatchBookmark feature ( kube-apiserver) which is GA since 1.17. It will also be used by a new WatchList and WatchListClient features which are targeted to Beta in this release (1.30) All GCE tests set the flag as well. Given the above, a default installation must pass the flag required by the kube-apiserver to etcd. Otherwise, some features will not work. etcd-io/etcd#13779 tracks stabilization of the flag in etcd.
This is tracking issue that tracks graduation of this feature. Let's work towards stabilization of the feature by discussing what steps should be taken for graduation.
Context #13775
The text was updated successfully, but these errors were encountered: