Drop Outgoing Traffic

This attack affects network traffic for protocols that use port numbers (e.g., TCP, UDP). Protocols like ICMP, which do not use ports, remain unaffected and will continue to function normally.

Use Cases

Understand how your services behave under specific / flaky network conditions

Parameters

Parameter	Description	Default
Duration	How long should the traffic be lost?	30s
Hostname	Restrict to which hosts the traffic is lost
IP Address	Restrict to which IP address the traffic is lost
Network Loss	How much percentage of traffic should be lost?	70
Network Interface	Target Network Interface which should be attacked. All if none specified.
Port Number	Restrict to which port number the traffic is delayed

Useful Templates

See all

Network loss for Kubernetes node's outgoing traffic in an availability zone

Achieve high availability of your Kubernetes cluster via redundancy across different Availability Zones. Check what happens to your Kubernetes cluster when one of the zones suffers from a network loss.

Motivation

Cloud provider host your deployments and services across multiple locations worldwide. From a reliability standpoint, regions and availability zones are most interesting. While the former refers to separate geographic areas spread worldwide, the latter refers to an isolated location within a region. For most use cases, applying deployments across availability zone is sufficient. Given that failures may happen at this level quite frequently, you should verify that your applications are still working in case of an outage.

Structure

We leverage the drop outgoing traffic to simulate network loss in an availability. If you want to test for a full outage of the zone, configure it to 100% loss. While the network loss happens, we observe changes of a Kubernetes cluster with Steadybit's built-in visibility. Once the network loss is over, we expect that all deployments will recover again within a specified time.