Ever since I upgraded to 0.9.0 (but now on 0.9.2) CronJob which can't be immediately scheduled are reported as "Errors: Reason Unschedulable".

I've a staging system where I also use kwatch, where often it takes multiple tries to schedule CronJob, therefore I want to ignore those errors.

For similar reasons I already have an existing config, here's my current (pre 0.9.0) ConfigMap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: kwatch
  namespace: kwatch
data:
  config.yaml: |
    alert:
      slack:
        webhook: …
        title: k8s-staging
    maxRecentLogLines: 10
    reasons:
      - '!CreateContainerConfigError'

Now I want to add Unschedulable to be ignored too, but nothing I tried worked:

• a separate line

      reasons:
        - '!CreateContainerConfigError'
        - '!Unschedulable'

• added to the existing one

      reasons:
        - '!CreateContainerConfigError,Unschedulable'

So far no luck: those errors are still coming.

I wrote:

Ever since I upgraded to 0.9.0

Basically, I'm pretty sure I was never notified of Unschedulable before (using 0.8.5).

Any idea what I'm doing wrong?