Pod Network Chaos Scenarios using Krknctl
krknctl run pod-network-chaos (optional: --<parameter>:<value> )
Can also set any global variable listed here
Scenario specific parameters:
| Parameter | Description | Type | Default |
|---|---|---|---|
| Namespace of the pod to which filter need to be applied | string | ||
| When pod_name is not specified, pod matching the label will be selected for the chaos scenario | string | ||
| When label_selector is not specified, pod matching the name will be selected for the chaos scenario | string | ||
| Targeted instance count matching the label selector | number | 1 | |
| List of directions to apply filters - egress/ingress ( needs to be a list ) | string | “[ingress,egress]” | |
| Ingress ports to block ( needs to be a list ) | string | ||
| Egress ports to block ( needs to be a list ) | string | ||
| Ensure that it is at least about twice of test_duration | number | 300 | |
| Duration of the test run | number | 120 |
To see all available scenario options
krknctl run pod-network-chaos --help
