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
Current network scenarios in Krkn support network traffic shaping at the node level: https://github.com/redhat-chaos/krkn/blob/main/docs/network_chaos.md in addition to application outage scenario that can block ingress/egress traffic to an application/pod: https://github.com/redhat-chaos/krkn/blob/main/docs/application_outages.md but not a specific port or shape the traffic like drop certain amount of packets/inject certain amount of latency at the pod level.
The text was updated successfully, but these errors were encountered:
Pod level network scenarios are now supported thanks to @yogananth-subramanian!
Sorry, something went wrong.
yogananth-subramanian
No branches or pull requests
Current network scenarios in Krkn support network traffic shaping at the node level: https://github.com/redhat-chaos/krkn/blob/main/docs/network_chaos.md in addition to application outage scenario that can block ingress/egress traffic to an application/pod: https://github.com/redhat-chaos/krkn/blob/main/docs/application_outages.md but not a specific port or shape the traffic like drop certain amount of packets/inject certain amount of latency at the pod level.
The text was updated successfully, but these errors were encountered: