POV validation guide

2 min read · Intermediate

This guide provides a structured framework for validating Edera during a proof of value (POV) evaluation. Each test demonstrates a core value proposition with measurable outcomes.

Overview

The POV validation framework consists of three 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, kbench
Operations	Verify integration with existing tools	Grafana observability, RuntimeClass automation

Prerequisites

Before running POV tests, ensure:

Access to the POV environment bastion host
AWS CLI configured with appropriate credentials
kubectl installed locally
helm installed (for optional components)

Connect to the bastion host

Follow the access instructions provided by Edera to connect to your POV environment bastion host.

Verify kubectl access

Confirm you can access the cluster:

kubectl get pods -n kube-system

Clone the test repository

git clone https://github.com/edera-dev/learn.git
cd learn/pov-validation

Verify the Edera RuntimeClass

The Edera RuntimeClass is pre-configured in your POV environment. Verify it’s available:

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 POV 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

Security demonstration Performance validation Operations integration

Last updated on 2026-02-10