Martin Linkhorst

Sounds good!

Do you mean that in order to reach a Pod's Deployment you have to read the owning ReplicaSet to get its owner? How about adding the event only on the...

I'm not a big fan of them but I also don't have much experience with them. From your linked article they provide exactly what I would like so I wouldn't...

Could we add a prometheus metric for that? I often saw some "binary" metrics that you are supposed to "query" via labels and then either return 0 or 1, e.g....

Not at all. I just wanted to provide an inferior alternative that might save us some effort. I'm fine with adding slack support. How about putting it in a separate...

Detection could be similar to: https://github.com/zalando-incubator/cluster-lifecycle-manager/blob/8042e37ad3fb482879112e8bc6d095c01ff2ef7c/pkg/updatestrategy/node_pool_manager.go#L481-L484

That would be a bit more work as `chaoskube` currently works solely on the Pod list. One would have to use the `ownerReferences` to find its `ReplicaSet` and from there...

I think this makes a lot of sense in order to start using `chaoskube` without unnecessary interruptions. There are applications that aren't high-available and if their single replica dies they...

I was thinking about making it pod specific but I also see value in a global version of it like you propose in https://github.com/linki/chaoskube/pull/34. For the pod specific version I...

makes sense, I'll add another issue as attributes may still be useful.