This commit is contained in:
lichuqiang 2017-08-18 08:42:47 +00:00
parent 429004fdf1
commit b581e8144b
1 changed files with 1 additions and 1 deletions

View File

@ -101,7 +101,7 @@ But, it seems fitting to recommend the following:
your application's resource profile during idle time too closely. 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 2. Always set limits so that your application doesn't hog all the memory on a
node during a spike. 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 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 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 try to access resources outside what it's guaranteed to have access to. As