Pod egress network shapping Chaos scenario #449
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chaitanyaenr
reviewed
Jul 5, 2023
|
/funtest |
paigerube14
reviewed
Jul 24, 2023
yogananth-subramanian
force-pushed
the
pod-network-traffic-shaping
branch
from
c0dad0e
to
6c3551a
Compare
|
Hello @chaitanyaenr @paigerube14, have update the PR, integrating "pod egress shaping" with "pod network outage", as a single plugin. Your review would be greatly appreciated. |
yogananth-subramanian
force-pushed
the
pod-network-traffic-shaping
branch
from
6c3551a
to
6a71015
Compare
chaitanyaenr
reviewed
Aug 1, 2023
chaitanyaenr
reviewed
Aug 1, 2023
chaitanyaenr
approved these changes
Aug 1, 2023
yogananth-subramanian
force-pushed
the
pod-network-traffic-shaping
branch
from
6a71015
to
13da539
Compare
The scenario introduces network latency, packet loss, and bandwidth restriction in the Pod's network interface.
The purpose of this scenario is to observe faults caused by random variations in the network.
Below example config applies egress traffic shaping to openshift console.
````
- id: pod_egress_shaping
config:
namespace: openshift-console # Required - Namespace of the pod to which filter need to be applied.
label_selector: 'component=ui' # Applies traffic shaping to access openshift console.
network_params:
latency: 500ms # Add 500ms latency to egress traffic from the pod.
````
yogananth-subramanian
force-pushed
the
pod-network-traffic-shaping
branch
from
13da539
to
1901186
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chaitanyaenr, yogananth-subramanian The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The scenario introduces network latency, packet loss, and bandwidth restriction in the Pod's network interface. The purpose of this scenario is to observe faults caused by random variations in the network.
Below example config applies egress traffic shaping to openshift console.