Add Kubernetes Native Deployment Support for FinalRip Microservices

[Copilot]

This PR introduces comprehensive Kubernetes-native deployment capabilities for FinalRip, providing a modern cloud-native alternative to the existing Docker Compose setup.

Overview

FinalRip currently uses Docker Compose for microservice orchestration with two deployment modes:

• Quick deployment: Single-host setup via docker-compose/lite/docker-compose.yml
• Distributed deployment: Multi-stage deployment across multiple hosts

This PR adds full Kubernetes support while maintaining compatibility with the existing Docker Compose approach.

What's Added

🏗️ Complete Kubernetes Manifests

• Infrastructure services: MongoDB, Redis, MinIO, Consul, AsynqMon
• Application services: Server, Dashboard, Workers (Cut/Merge/Encode)
• Configuration management: ConfigMaps and Secrets
• Networking: Services and Ingress controllers
• Storage: Persistent Volume Claims for data persistence

📦 Multiple Deployment Options

1. Kustomize-based Deployment

# Development environment
kubectl apply -k deploy/k8s/overlays/development

# Production environment with enhanced resources
kubectl apply -k deploy/k8s/overlays/production

2. Helm Charts

# Simple installation
helm install finalrip deploy/k8s/helm/finalrip

# Custom configuration
helm install finalrip deploy/k8s/helm/finalrip -f custom-values.yaml

3. Automated Scripts

# One-click deployment
./deploy/k8s/deploy.sh development

# Clean removal
./deploy/k8s/undeploy.sh

🚀 Key Improvements Over Docker Compose

Feature	Docker Compose	Kubernetes Native
Scaling	Manual, single-host limited	Auto/manual, multi-node
High Availability	Single point of failure	Multi-replica with auto-recovery
Configuration	Environment files	ConfigMaps + Secrets
Service Discovery	Container names	Kubernetes DNS
Load Balancing	Basic round-robin	Advanced traffic management
Health Checks	Basic	Comprehensive liveness/readiness probes
Rolling Updates	Manual coordination	Zero-downtime deployments

🎯 Production-Ready Features

• GPU Support: Optimized worker-encode deployment with NVIDIA GPU scheduling
• Resource Management: CPU/Memory requests and limits for all services
• Persistent Storage: Proper volume management for databases and file storage
• Security: RBAC, Network Policies, and Secret management
• Monitoring: Built-in health checks and observability hooks
• Autoscaling: Horizontal Pod Autoscaler configuration

📚 Comprehensive Documentation

• deploy/k8s/README.md: Complete deployment guide with troubleshooting
• deploy/k8s/COMPARISON.md: Detailed comparison between Docker Compose and Kubernetes approaches (Chinese)
• Architecture diagrams: Service dependencies and networking topology

File Structure

deploy/k8s/
├── base/                    # Base Kubernetes manifests
├── overlays/               # Environment-specific configurations
│   ├── development/        # Dev environment with reduced resources
│   └── production/         # Prod environment with HA and scaling
├── helm/finalrip/          # Helm chart for parameterized deployment
├── deploy.sh              # Automated deployment script
├── undeploy.sh            # Cleanup script
├── README.md              # Comprehensive deployment documentation
└── COMPARISON.md          # Docker Compose vs Kubernetes comparison

Migration Path

The implementation supports gradual migration:

1. Parallel deployment: Run K8s alongside existing Docker Compose
2. Service-by-service migration: Move individual components incrementally
3. Data migration: Tools and procedures for database/storage migration
4. Complete cutover: Full transition to Kubernetes-native deployment

GPU Acceleration Support

Special attention has been given to the video encoding workload:

resources:
  requests:
    nvidia.com/gpu: 1
  limits:
    nvidia.com/gpu: 1
nodeSelector:
  accelerator: nvidia-tesla-gpu

Backward Compatibility

This PR is completely additive - all existing Docker Compose configurations remain unchanged and functional. Teams can choose their preferred deployment method or migrate at their own pace.

The Kubernetes deployment maintains the same service architecture, API endpoints, and functionality as the Docker Compose version, ensuring seamless operation regardless of the chosen deployment method.

---

💡 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.