kube-monkey schedules Termination successfully, but POD always doesn't be killed about kube-monkey

[kyrylyuk-andriy]

I have the same issue, deployments are scheduled to be terminated but not all of them actually were terminated (pods in a deployment)

[worldtiki]

Can you share the configs for kube monkey that you are using?

[kyrylyuk-andriy]

my kube-monkey tool config

config:
  dryRun: false
  runHour: 11
  startHour: 12
  endHour: 13
  blacklistedNamespaces: [ "kube-system", "istio-system", "rbac-manager", "db-migrate" ]
  whitelistedNamespaces: [ "default"]
  timeZone: America/New_York
  debug:
   enabled: false # if you want to enable debugging and see how pods killed immediately set this to true
   schedule_immediate_kill: false

and labels in each opted in service

metadata:
  labels:
    kube-monkey/enabled: enabled
    kube-monkey/identifier: kube-monkey-victim
    kube-monkey/kill-mode: fixed
    kube-monkey/kill-value: "3"
    kube-monkey/mtbf: "1"
spec:
  template:
    metadata:
      labels:
        kube-monkey/enabled: enabled
        kube-monkey/identifier: kube-monkey-victim

this labels config use around 10-12 different services, all of them were scheduled for termination with pre defined hours and only 3-4 services (pods) were actually were terminated,

[worldtiki]

Do you mind adding the logs, the version that you are using and more detail?
Is it always the same services that are not attacked or is ti random?

[kyrylyuk-andriy]

i ran only once in production environment, i stopped until we figure out how this tool works, in logs we was that tool triggered termination for deployments but we didn't see any terminated pods after that.

our kube-monkey version

image: ayushsobti/kube-monkey:v0.3.0

[worldtiki]

Sorry for the radio silence @kyrylyuk-andriy. A new version was released yesterday if you want to give it a try.