Commits on Dec 3, 2017

1. Add option to apply caps only on alive pods …

   A pod can be in one of five phases: running, pending, succeeded, failed
   or unknown. The pods which are not in the running/pending phase do not
   consume any CPU/Memory resources, they just need to be GC'ed. If, in the
   scenario when a cap has been specified on a k8s cloud (single namespace)
   and let's say 40% of the count are in the 'failed' phase, and 60% are
   'runnning/pending', newer pods will not be spawned in that namespace,
   since the plugin will count all those pods for instance/pod cap and even
   though it could have spawned 40% more pods, it won't and jobs will
   starve. This patch adds an option to calculate the cap for pods only in
   the 'running' or 'pending' phase, on a cloud level and on a pod template
   level, so that the cap applies to only those pods which are alive or
   about to be.
   
   Change-Id: Id77e837aa9a42742618cd3c543e7b99f9d38a10a

   

   nehaljwani committed Dec 3, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for a615156
   • Browse repository at this point

   Copy the full SHA

   a615156 View commit details

   Browse the repository at this point in the history