How cloud-bulldozer/k8s-netperf works
Main Components Identification
a. Core Components:
• Test Orchestrator (main application)
• Test Drivers (netperf, iperf3, uperf)
• Kubernetes Integration Layer
• Results Processor
• Metrics Collector
b. External Components:
• Kubernetes API Server
• Prometheus
• OpenSearch
• Test Pods/VMs (Client & Server)
• k8s-netperf System |
• Config | | Test Orchestrator| | Driver Manager | | Results Manager | |
• Management |---->| (Main Logic) |----->| (netperf/iperf) |----->| & Aggregator | |
• ^ | | | |
• v v v |
• Test Config | | K8s Interface | | Test Executor | | Metrics Collector| |
• Parser | | Layer | | | | & Reporter | |
• v v v
• Kubernetes | | Test Pods/VMs | | External Systems |
• API Server | | Client/Server | | - Prometheus |
• OpenSearch |
Component Relationships
Following interactions:
• Config flow: Config file → Config Parser → Test Orchestrator
• Test execution flow: Orchestrator → Driver Manager → Test Executor → Pods/VMs
• Results flow: Test Executor → Results Manager → External Systems
• Kubernetes interaction: K8s Interface Layer ↔ Kubernetes API Server
Key Elements to Highlight
• Multiple test driver support (netperf, iperf3, uperf)
• Pod and VM deployment capabilities
• Metrics collection and reporting paths
• Configuration management flow
• Results processing and storage pipeline
Additional Details
Annotations for:
• Supported test types (TCP_STREAM, UDP_STREAM, etc.)
• Network topology options (same node, across nodes)
• Performance metrics collection points
• Data export formats (CSV, JSON)