Solutions › Virtualization
Managed Kata Containers
VM-isolated pods on Kubernetes for workloads that need a hard security boundary
Kata Containers run selected pods inside lightweight virtual machines instead of sharing the node kernel. We operate the Kata runtime class on dedicated node pools of your managed Kubernetes cluster, so untrusted or regulated workloads get VM-level isolation with the same deployment workflow as every other pod.
How we run it
Service Operation Modes
Every managed service runs in one of two operation modes. Choose the mode that fits your availability requirements.
Basic Operation
Standard single-instance deployment. Suitable for development, staging, and non-critical production workloads.
- Single instance deployment
- Standard configuration
- Manual recovery on failure
- Lower cost
High Availability
Multi-instance deployment with automatic failover and redundancy. For production workloads that demand uptime.
- Multi-instance with redundancy
- Automatic failover
- Load-balanced traffic
- Zero-downtime maintenance
Included with every managed service
Monitoring
24/7 health checks, alerts, and performance tracking
Backup
Automated backups, freshness monitored and alerted
Patching
Security updates and version upgrades in staged monthly windows
Support
Direct access to the engineers who run your setup
Ingress NGINX Retirement: Why We Didn't Switch to Gateway API Yet
- Why we postponed Gateway API despite 5 years of spec development
- 20+ controllers evaluated across 6 weighted criteria
- Step-by-step migration with annotation translation table