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.

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

Added Rescheduler documentation #1170

Merged
merged 1 commit into from
Sep 16, 2016

Conversation

piosz
Copy link
Member

@piosz piosz commented Sep 6, 2016

In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
there is a bunch of addons which due to various reasons have to run on a regular cluster node, not the master.
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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would re-phrase this as "Thus a cluster may stop working properly if a critical addon is evicted (either manually or as a side effect of another operation like upgrade) and becomes pending (for example when the cluster is highly utilized and either there are other pending pods that schedule into the space vacated by the evicted critical addon pod or the amount of resources available on the node changed for some other reason."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@davidopp
Copy link
Member

davidopp commented Sep 7, 2016

I'm not done reviewing but some other higher-priority stuff popped up, so this will be delayed. Please wait to make changes until I'm done reviewing, otherwise it will be too confusing.


## Rescheduler: guaranteed scheduling of critical addons

Rescheduler ensures that critical addons are always scheduled (assuming the cluster is big enough).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/scheduled/running/

Instead of "assuming the cluster is big enough" I would say "assuming the cluster has enough resources to run the critical addon pods in the absence of regular pods"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not exactly true. If there is a problem with downloading docker image for DNS, the pod won't be running and Rescheduler can't fix this situation.

Applied the second comment.

@davidopp
Copy link
Member

davidopp commented Sep 7, 2016

ok done reviewing now

@devin-donnelly
Copy link
Contributor

@davidopp 's comments addressed any issues I had for Docs LGTM. Once he gives his LGTM, I'm good, too.

@piosz
Copy link
Member Author

piosz commented Sep 12, 2016

@davidopp comments addressed. PTAL

Copy link
Contributor

@devin-donnelly devin-donnelly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of small docs issues.

* TOC
{:toc}

# "Guaranteed" scheduling of critical addon pods
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addon -> add-on

Probably should be a global replacement throughout the document.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

## Critical addons

In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
there are a number of addons which due to various reasons have to run on a regular cluster node, not the master.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"which due to various reasons" -> "which, for various reasons, must run on a regular cluster node (rather than the Kubernetes master)."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
there are a number of addons which due to various reasons have to run on a regular cluster node, not the master.
Some of them are critical to have a fully functional cluster: Heapster, DNS, UI.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Some of these add-ons are critical to a fully functional cluster, such as Heapster, DNS, and UI."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
there are a number of addons which due to various reasons have to run on a regular cluster node, not the master.
Some of them are critical to have a fully functional cluster: Heapster, DNS, UI.
Thus a cluster may stop working properly if a critical addon is evicted (either manually or as a side effect of another operation like upgrade)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove "Thus" and capitalize "A cluster".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

* on running cluster by deleting its manifest from master node
(default path `/etc/kubernetes/manifests/rescheduler.manifest`)

### Marking addon as crticical
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

crticical -> critical

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@piosz
Copy link
Member Author

piosz commented Sep 16, 2016

Comments applied. PTAL

@devin-donnelly
Copy link
Contributor

Thank you, @piosz ! Merging now.

@devin-donnelly devin-donnelly merged commit 56de4ad into kubernetes:release-1.4 Sep 16, 2016
mikutas pushed a commit to mikutas/k8s-website that referenced this pull request Sep 22, 2022
* Add heroes for July and August (kubernetes#304)

Signed-off-by: Christian Mejlak <[email protected]>
Okabe-Junya pushed a commit to Okabe-Junya/website that referenced this pull request Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants