Add Kubernetes native deployment support for FinalRip microservices

[Copilot]

This PR adds comprehensive Kubernetes native deployment support to FinalRip, allowing users to deploy the distributed video processing system using modern cloud-native practices alongside the existing Docker Compose deployment option.

Overview

FinalRip currently uses Docker Compose for deployment, which works well for single-host scenarios but has limitations for production-scale distributed deployments. This implementation provides a complete Kubernetes deployment solution that offers better scalability, high availability, and operational capabilities.

What's Added

Complete Kubernetes Manifests (deploy/k8s/manifests/)

• Namespace isolation with dedicated finalrip namespace
• Configuration management using ConfigMaps and Secrets
• Persistent storage with PersistentVolumes and PersistentVolumeClaims
• All microservices including:
  • FinalRip Server (REST API)
  • Dashboard (Web UI)
  • Worker nodes (Cut, Merge, Encode with GPU support)
  • Infrastructure services (MongoDB, Redis, MinIO, Consul, Asynqmon)

Cloud-Native Features

• Auto-scaling with HorizontalPodAutoscaler for worker nodes (1-10 replicas based on CPU/memory)
• Health checks with liveness and readiness probes
• Resource management with CPU/memory limits and requests
• GPU support for encode workers with proper node selection and tolerations
• Ingress configuration for unified domain-based access

Multi-Environment Support

• Development overlay (overlays/development/) with reduced resource requirements
• Production overlay (overlays/production/) with production-grade resource allocation
• Kustomize support for easy environment-specific customization

Operational Tools

• One-click deployment script (deploy.sh) with apply/delete/status commands
• Configuration validation script (validate.sh) for pre-deployment checks
• Comprehensive documentation including migration guide and operational procedures

Deployment Comparison

Before (Docker Compose)

# Multi-step distributed deployment
docker-compose -f deploy/docker-compose/docker-compose-base.yml up -d
docker-compose -f deploy/docker-compose/docker-compose-server.yml up -d
docker-compose -f deploy/docker-compose/docker-compose-encode.yml up -d

After (Kubernetes)

# Single command deployment
cd deploy/k8s && ./deploy.sh apply

# Or environment-specific deployment
kubectl apply -k deploy/k8s/overlays/production/

Access Improvements

The new deployment provides cleaner access patterns:

• Dashboard: http://finalrip.local (vs http://localhost:8989)
• API: http://finalrip.local/api (vs http://localhost:8848)
• Monitoring: http://asynqmon.finalrip.local (vs http://localhost:8080)
• Storage Console: http://minio.finalrip.local (vs http://localhost:9001)

Key Benefits

1. High Availability: Multi-node deployment with automatic failover
2. Auto-scaling: Automatic worker scaling based on load (especially useful for encode workers)
3. Resource Efficiency: Precise CPU/memory/GPU resource management
4. Zero-downtime Updates: Rolling deployments for seamless updates
5. Better Observability: Built-in health checks and Kubernetes-native monitoring
6. GPU Optimization: Smart scheduling of encode workers to GPU-enabled nodes

Backward Compatibility

This change is fully backward compatible. Users can continue using Docker Compose deployment while having the option to migrate to Kubernetes for enhanced capabilities. The main README.md has been updated to document both deployment methods.

Documentation

Added comprehensive documentation:

• deploy/k8s/README.md: Complete deployment guide with prerequisites and configuration
• deploy/k8s/MIGRATION.md: Detailed comparison between Docker Compose and Kubernetes deployments
• Updated main README.md: Shows both deployment options with clear migration path

This implementation transforms FinalRip from a Docker Compose application into a production-ready cloud-native solution while maintaining the simplicity of the original deployment for development use cases.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.