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
One class of network chaos to support is for pod networking (vs host/node networking). Scenarios might be:
One possible way for Kraken to support these scenarios is via integration of Litmus experiments: Pod network latency Pod network loss Pod network corruption
This issue might need to be broken out into multiple issues.
The text was updated successfully, but these errors were encountered:
This is now supported in Krkn thanks to @yogananth-subramanian at both pod and node level: https://github.com/redhat-chaos/krkn/blob/main/docs/pod_network_scenarios.md and https://github.com/redhat-chaos/krkn/blob/main/docs/network_chaos.md. Thanks.
Sorry, something went wrong.
No branches or pull requests
One class of network chaos to support is for pod networking (vs host/node networking). Scenarios might be:
-networks that are expected to periodically disconnect (moving vehicles)
One possible way for Kraken to support these scenarios is via integration of Litmus experiments:
Pod network latency
Pod network loss
Pod network corruption
This issue might need to be broken out into multiple issues.
The text was updated successfully, but these errors were encountered: