C3 - Testing
7 minute read
How metarex can build an API to cost your running cloud
The development testbed will consist of 2 different high availability Kubernetes cluster types, each running the same kubernetes pods on different node types. Identical infrastructure (otel, metarex, prometheus, grafana) will be used to extract, store and present the results.
- Groups A cluster - Amazon EKS
Using the native Amazon Kubernetes infrastructure to host the test environment - in theory, this should be the most controllable running on AWS - Group R cluster - Rancher K3s
Designed to run with the same definitions as Group A - in theory this should be portable across platfrom so that we can measure a baseline infrastructure cost and isolate the executable code costs more accurately. - TBD - GKE - Google’s Kubernetes Engine for native costs
- TBD - AKS - Microsoft Azure Kubernetes Service for native costs
- TBD - ACK - Alibaba Cloud for Kubernetes native costs
I asked Claude (Anthropic Sonnet 4.0) to estimate the costs of the proposed comparison architecture
Quick Comparison Table
Feature | Group A (EKS) | Group R (k3s) |
---|---|---|
Management | Fully managed control plane | Self-managed |
Monthly Cost | ~$248 | ~$195 |
Setup Time | ~15 minutes | ~20 minutes |
Control Plane HA | AWS managed (3 AZs) | Self-managed etcd cluster |
Node Management | Managed node groups | Manual EC2 instances |
Networking | VPC CNI | Flannel CNI |
Load Balancing | AWS LoadBalancer Service | Caddy NodePort + NLB |
Storage | EBS CSI Driver | Local-path provisioner |
Monitoring | CloudWatch integration | Prometheus/Grafana |
Upgrades | Managed | Manual |
Scalability | Auto-scaling groups | Manual scaling |
Complexity | Medium | Low |
Architecture Comparison
Group A (EKS) Architecture
Internet β AWS ALB β EKS Managed Nodes β Pods
β
VPC CNI β ENI per Pod
β
EBS CSI β Persistent Volumes
β
CloudWatch β Monitoring
Group R (k3s) Architecture
Internet β NLB β NodePort (30080) β Caddy Pods β Apps
β
Flannel β VXLAN Overlay
β
Local Storage β Persistent Volumes
β
Prometheus β Monitoring
Detailed Feature Comparison
1. Control Plane Management
Group A (EKS):
- AWS manages etcd, API server, scheduler, controller manager
- Automatic backups and disaster recovery
- Multi-AZ deployment by default
- Managed security patches and updates
- 99.95% SLA
Group R (k3s):
- Self-managed embedded etcd cluster
- Manual backup strategy required
- HA through multiple controller nodes
- Manual security updates needed
- Depends on EC2 SLA (99.99%)
2. Networking
Group A (EKS):
Group R (k3s):
3. Storage Options
Group A (EKS):
- EBS CSI driver for persistent volumes
- EFS CSI driver for shared storage
- FSx integration available
- Automatic volume provisioning
- Cross-AZ volume attachment
Group R (k3s):
- Local-path provisioner (default)
- Manual EBS integration possible
- Simpler storage model
- Node-local storage binding
- Manual backup strategies
4. Load Balancing
Group A (EKS):
Group R (k3s):
|
|