This set of events would only work in the context of a self-hosted k8s cluster, so they cannot be included in the all khaotic events set.
With the components (apiserver, scheduler, kubelet, controller-manager, etc.) being run as pods in the cluster, we could make events to target these pieces.
These should be easily recoverable, as they are managed pods. Configuring it to cripple the control plane would be a nice test of the cluster's robustness as well as that of the deployed applications.
I'm curious how closely something like this relates to a kubernetes soak test. This feels like it could be used to implement a localized version of that.
This set of events would only work in the context of a self-hosted k8s cluster, so they cannot be included in the
all
khaotic events set.With the components (apiserver, scheduler, kubelet, controller-manager, etc.) being run as pods in the cluster, we could make events to target these pieces.
These should be easily recoverable, as they are managed pods. Configuring it to cripple the control plane would be a nice test of the cluster's robustness as well as that of the deployed applications.
@swade1987 && @jbowen93 ?