Advanced Networking
Deep dive into Kova networking architecture.
Network Architecture
Internet → Apache (SSL) → Orchestrator Ingress → Provider Container
Components
-
Apache Reverse Proxy
- Handles SSL/TLS termination
- Routes based on subdomain
- Manages Let's Encrypt certificates
-
Orchestrator Ingress
- Maintains deployment → provider mapping
- Proxies requests to correct provider
- Handles health checks
-
Provider Container
- Docker container running your app
- Accessible via internal port mapping
DNS and Subdomains
Each deployment gets a unique subdomain:
{service}-{deployment-id}.deployments.kovanetwork.com
Example:
web-17628738.deployments.kovanetwork.com
Custom Domains
Custom domain support is planned for future releases. Currently, all deployments use the *.deployments.kovanetwork.com subdomain.
Inter-Service Communication
Services within the same deployment communicate via Docker DNS:
services:
api:
env:
- DATABASE_HOST=db # Uses service name
- REDIS_HOST=cache
db:
image: postgres:15
cache:
image: redis:alpine
Internal service communication doesn't go through the public internet. It stays within the Docker network on the provider.