Getting started with validation
This guide provides a structured framework for validating Edera. Each test demonstrates a core capability with measurable outcomes. It’s designed for anyone evaluating Edera—whether you’re running a proof of value, trying the free tier, or just getting started.
Overview
The validation framework consists of the following test suites:
| Suite | Purpose | Tests |
|---|---|---|
| Security | Validate container isolation and escape prevention | RuntimeClass setup, Leaky Vessel demo, Falco integration |
| Performance | Benchmark network and CPU performance | iperf, sysbench |
| CPU benchmarking | Multi-threaded CPU validation with annotations | sysbench |
| Memory benchmarking | Memory bandwidth validation with thread matching | sysbench |
| Operations | Verify integration with existing tools | Grafana observability, RuntimeClass automation |
Prerequisites
Before running validation tests, ensure:
- SSH access to a node with Edera installed
- AWS CLI configured with appropriate credentials
- kubectl installed locally
- helm installed (for optional components)
Verify kubectl access
Confirm you can access the cluster:
kubectl get pods -n kube-systemClone the test repository
git clone https://github.com/edera-dev/learn.git
cd learn/validateVerify the Edera RuntimeClass
Verify the Edera RuntimeClass is available on your cluster:
kubectl get runtimeclass edera
kubectl get nodes -l runtime=ederaℹ️
Nodes with the
runtime=edera label have the Edera runtime installed and can run isolated workloads.Success criteria
A successful validation demonstrates:
- Technical validation: Workloads deploy and run with the Edera runtime
- Security demonstration: Container escape attempts are blocked
- Performance validation: Network and CPU performance meet baseline expectations
- Observability integration: Metrics are visible in Grafana
- Workflow compatibility: Existing tools and processes work unchanged
Test suites
Last updated on