MpegFlowBlogBack to home
← Topics·2 pieces

Operator

The Kubernetes operator pattern for multi-tenant video transcoding gives you per-tenant pool isolation as a CRD, leader election for HA, pool-pause for drain-without-drop upgrades, and per-pool routing that keeps the topology out of your application layer. These pieces cover the operator design and where it earns its keep above the simpler worker-Deployment pattern.

Reference architectures · 1
  • Kubernetes deployment with KEDA autoscaling
    Production K8s topology for MpegFlow — API tier, shared workers via Helm, dedicated workers via Operator, KEDA queue-depth autoscaling, leader election, pool pause for cost savings.
    May 5, 2026
Engineering blog · 1
  • FFmpeg in Kubernetes: the pod, queue, and operator pattern
    How to run FFmpeg in Kubernetes at production scale — the four patterns we've watched teams climb, where each breaks, and why a video transcoder Kubernetes operator earns its keep above ~50K jobs/day.
    May 8, 2026
Adjacent topics
  • Kubernetes· 3
  • FFmpeg· 3
  • KEDA· 1
  • Autoscaling· 2
  • Helm· 1
© 2026 MpegFlow, Inc. · Trust & complianceAll systems nominal·StatusPrivacy