Martin Linkhorst
Martin Linkhorst
Alternative implementation for https://github.com/linki/chaoskube/pull/108
Based on the feedback in https://github.com/linki/chaoskube/issues/275#issuecomment-805066591 by @javajon.
Based on https://github.com/linki/chaoskube/pull/108 implements a different approach to solve https://github.com/linki/chaoskube/issues/92.
In order to simulate an outage of an entire node or availability zone, we could add some kind of selection based on topology keys. For instance, starting chaoskube with ```...
The number of arguments for `Chaoskube.New()` has increased to a point where it becomes annoying to use. We could switch to a struct to have order-independent arguments by Name. It...
See https://github.com/linki/chaoskube/issues/75 If chaoskube has trouble talking to Kubernetes (during runtime) it should be detectable either via readiness/healthiness probes or via metrics.
I'm a metrics newbie. Time to play around on a simple project like this. * time to filter pods (I guess it's quite expensive the way it's implemented now) *...
Currently `chaoskube` requires global `pod-reader` to find targets even when narrowing down the search space with the `--namespaces` flag. See: https://github.com/linki/chaoskube/blob/v0.9.0/chaoskube/chaoskube.go#L144 Deletion works fine as the API targets a specific...
static pods cannot be killed via the Kubernetes API: https://kubernetes.io/docs/tasks/administer-cluster/static-pod/ Let's ignore them. We could use these annotations to detect what is a static pod: ``` metadata: annotations: kubernetes.io/config.hash: 3ffad4b19c937d5bb9cbacadb2f463a1...
Currently, the probability of a pod being killed depends on the number of pods being in the target group. This is bad if you want to run `chaoskube` as a...