OSO Kafka Backup can be deployed in several ways depending on your infrastructure and requirements.
Deployment Options
| Method | Best For | Management | Scalability |
|---|
| Bare Metal | Traditional servers, VMs | Manual | Manual |
| Docker | Containerized environments | Manual/Compose | Manual |
| Kubernetes | K8s clusters (manual) | kubectl/Helm | Manual |
| Kubernetes Operator | Production K8s | CRDs/GitOps | Automatic |
Quick Decision Guide
- Running on traditional servers or VMs
- Simple single-node deployments
- Direct filesystem access required
- Minimal container overhead desired
Use Docker When
- Local development and testing
- CI/CD pipelines
- Simple container deployments
- Docker Compose environments
Use Kubernetes When
- Running on Kubernetes clusters
- Need manual control over backup scheduling
- Using external job schedulers (Argo, Airflow)
- Not ready for operator pattern
Use Kubernetes Operator When
- Production Kubernetes deployments
- GitOps workflows (ArgoCD, Flux)
- Automated scheduled backups
- Multi-tenant environments
- Need declarative backup management
System Requirements
Minimum Requirements
| Resource | Requirement |
|---|
| CPU | 1 core |
| Memory | 256 MB |
| Disk | 10 GB (+ backup storage) |
| Network | Access to Kafka brokers |
Recommended for Production