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

fix typo in docs/node_resource_handling.md #3233

Merged
merged 1 commit into from
Aug 18, 2017
Merged

fix typo in docs/node_resource_handling.md #3233

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
2 changes: 1 addition & 1 deletion docs/node_resource_handling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ But, it seems fitting to recommend the following:
your application's resource profile during idle time too closely.
2. Always set limits – so that your application doesn't hog all the memory on a
node during a spike.
3. Don't set your limits for imcompressible resources too high - at the end of
3. Don't set your limits for incompressible resources too high - at the end of
the day, the Kubernetes scheduler schedules based on resource requests which
match what's available on the node. During a spike, your pod technically will
try to access resources outside what it's guaranteed to have access to. As
Expand Down