-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Prioritized scheduling of critical cluster addon pods #62
Comments
cc @kubernetes/sig-scheduling |
OK I updated it. |
Status: this feature is finished except for docs. The code is in contrib/rescheduler and it will be automatically deployed in clusters, requesting 10m cpu and 100Mi memory. This feature does not have an API (perhaps you could call its flags an API, but not in the usual Kubernetes API sense) so I am not sure whether to call this alpha, beta, or GA. I guess I'll call it alpha. |
@davidopp re: alpha/beta/stable - are we planning on doing more work here in 1.5 or have significant iterations to do? Do we have reason to recommend not using it in production clusters? Basically - why isn't this GA/stable? |
Here are some random thoughts:
I'm fine calling it beta, though I think we should try to limit the number of features that go directly to beta. |
@davidopp @piosz Are the docs ready? Please update the docs in https://github.com/kubernetes/kubernetes.github.io, and then add PR numbers and check the docs box in the issue description |
@janetkuo PR kubernetes/website#1170 in flight |
@piosz Should we close this issue? IIUC we're not planning to do more work on it, and it runs by default in all clusters (GKE and open-source). If you agree, please close. |
Yes we should close this. I don't have enough permissions to do it. |
This feature still seems to be marked alpha (at least the annotation is still marked alpha). Has this been abandoned without plans to move it to beta? |
It will not move to beta. It will be subsumed by #268. |
…olm-folder Move olm registry enhancement to correct folder
Description
Kubernetes has "cluster addon pods" that provide system services but do not run on the master node. Some of them are critical to have fully functional cluster: Heapster, DNS, UI. Users can break their cluster by evicting a critical addon (either manually or as a side effect of an other operation like upgrade) which possibly can become pending (for example when the cluster is highly utilized). To avoid such situation we introduce a rescheduler component that runs on the master and guarantees that critical addons are scheduled assuming the cluster is big enough. It does this by watching for pending critical pods and evicting other pods to make room for the pending one(s).
Design Proposal: kubernetes/kubernetes#29195
Progress Tracker
FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design
Coding
and sometimes http://github.com/kubernetes/contrib, or other repos.
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing. They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.
Docs
The text was updated successfully, but these errors were encountered: