[Workload]: chaos-network workload (tc/netem-based latency, packet loss, bandwidth limiting)

[mrhillsman]

Workload Name

chaos-network

Workload Description

This workload uses tc qdisc and netem to inject configurable network chaos into a VM. It simulates degraded network conditions including:

• Configurable latency injection (default 100ms)
• Packet loss (default 5%)
• Bandwidth limits
• Advanced network emulation: jitter, reordering, duplication

The workload runs as a systemd service with configurable duration and interval.

Tooling and Packages

• Tool: tc (traffic control), netem
• RPM packages: iproute-tc (pre-installed via golden image, see [Feature]: Golden container disk image with pre-installed workload tools #16)
• Additional tools: iptables-nft for network partition simulation
• systemd service command: tc qdisc add/change with netem parameters

VM Count Model

Single VM (like cpu, memory, disk)

Required Resources

• Persistent storage (DataVolume)
• Kubernetes Service (for inter-VM communication)
• Kubernetes Secret (for credentials or config)
• Additional CPU/memory beyond defaults
• GPU or special device passthrough

Cloud-Init Details

Packages: pre-installed via golden image (#16)
Systemd unit: tc netem configuration with Restart=always
Write files: optional /etc/virtwork/chaos-network.conf for parameters

Use Case

Network chaos injection for validating application resilience under degraded network conditions. Useful for testing Prometheus alerting rules for network latency, validating service mesh timeout configurations, and verifying application retry logic under packet loss.

Additional Context

Depends on golden container disk image (#16) for pre-installed tc and iproute-tc.

Related Issues: #16 (golden image dependency)

Split from #15