Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for terminating multiple pods within a topology #241

Open
linki opened this issue Aug 12, 2020 · 0 comments
Open

Add support for terminating multiple pods within a topology #241

linki opened this issue Aug 12, 2020 · 0 comments

Comments

@linki
Copy link
Owner

linki commented Aug 12, 2020

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

--topology-key=kubernetes.io/zone

Could batch-kill all pods within a single zone per iteration.

Similarly,

--topology-key=kubernetes.io/node
--topology-key=kubernetes.io/region

would batch-kill all Pods of a single node or region, respectively.

Combined with the already existing --max-kill flag (default 1) one could trigger deletions for multiple nodes, zones etc.

Furthermore,

--topology-key=kubernetes.io/pod

would be equivalent to the current behaviour, I believe.

Pods would probably restart on the same nodes after being terminated but it might still be useful to simulate full node or zone outages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant