We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
--max-kill
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
Could batch-kill all pods within a single zone per iteration.
Similarly,
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,
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.
The text was updated successfully, but these errors were encountered: