gasildeal.blogg.se

California reaper pods
California reaper pods












12 * * * * * for example will run on the 12th second of every minute. The cron parser used can optionally support seconds if a sixth parameter is add. But more complex use cases can make use of the * * * * * notation. For most use cases, the interval format 1h2m3s is sufficient. The format follows the upstream cron library.

california reaper pods

SCHEDULEĬontrols how frequently pod-reaper queries kubernetes for pods. A duration of 0s can be considered a hard kill of the pod. The format follows the go-lang time.duration format (example: "1h15m30s"). This will determine the time between when the pod's containers are send a SIGTERM signal and when they are sent a SIGKILL signal. GRACE_PERIODĭefault value: nil (indicates to the use the default specified for pods)Ĭontrols the grace period between a soft pod termination and a hard termination. Only pods (and namespaces) accessible to this service account will be visible to the pod-reaper. Note that the pod-reaper uses an InClusterConfig which makes use of the service account that kubernetes gives to its pods. See the Rules section below for configuring and enabling rules.ĭefault value: "" (which will look at ALL namespaces)Ĭontrols which kubernetes namespace the pod-reaper is in scope for the pod-reaper. LOG_FORMAT choose between several formats of loggingĪdditionally, at least one rule must be enabled, or the pod-reaper will error and exit.LOG_LEVEL control verbosity level of log messages.POD_SORTING_STRATEGY sorts pods before killing them (most useful when used with MAX_PODS).MAX_PODS kill a maximum number of pods on each run.DRY_RUN log pod-reaper's actions but don't actually kill any pods.REQUIRE_ANNOTATION_VALUES comma-separated list of metadata annotation values (of key-value pair) that pod-reaper should require.REQUIRE_ANNOTATION_KEY pod metadata annotation (of key-value pair) that pod-reaper should require.REQUIRE_LABEL_VALUES comma-separated list of metadata label values (of key-value pair) that pod-reaper should require.REQUIRE_LABEL_KEY pod metadata label (of key-value pair) that pod-reaper should require.EXCLUDE_LABEL_VALUES comma-separated list of metadata label values (of key-value pair) that pod-reaper should exclude.

california reaper pods

EXCLUDE_LABEL_KEY pod metadata label (of key-value pair) that pod-reaper should exclude.EVICT try to evict pods instead of deleting them.RUN_DURATION how long pod-reaper should run before exiting.SCHEDULE schedule for when pod-reaper should look for pods to reap.GRACE_PERIOD duration that pods should be given to shut down before hard killing the pod.NAMESPACE the kubernetes namespace where pod-reaper should look for pods.

california reaper pods

The pod-reaper specific environment variables are: Pod-Reaper is configurable through environment variables. See the "Implemented Rules" section below for details on specific rules. Pod-Reaper was designed to kill pods that meet specific conditions.














California reaper pods