https://www.pistack.xyz/tags/scheduling/Recent content in Scheduling on Pi StackHugoen-usTue, 21 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/volcano-vs-yunikorn-vs-kueue-kubernetes-batch-scheduler-guide-2026/Tue, 21 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/volcano-vs-yunikorn-vs-kueue-kubernetes-batch-scheduler-guide-2026/<p><a href="https://kubernetes.io/">kubernetes</a> was designed primarily for long-running services, not batch workloads. The default scheduler makes no distinction between a web server that needs to stay up 24/7 and a data processing job that should run to completion and exit. For organizations running high-performance computing (HPC), machine learning training, ETL pipelines, or any job-queueing workload on self-hosted Kubernetes clusters, the default scheduler falls short.</p>https://www.pistack.xyz/posts/self-hosted-cron-job-schedulers-cronicle-rundeck-go-autocomplete-guide-2026/Thu, 16 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/self-hosted-cron-job-schedulers-cronicle-rundeck-go-autocomplete-guide-2026/<h2 id="why-self-host-your-cron-job-scheduler">Why Self-Host Your Cron Job Scheduler?</h2> <p>The traditional Unix <code>crontab</code> has been the backbone of scheduled task execution for decades. It is simple, reliable, and available on every Linux system. But as infrastructure grows in com<a href="https://www.plex.tv/">plex</a>ity, plain crontab reveals critical shortcomings that make it unsuitable for modern operations:</p>