Guide

DEVOPS & TIME UTILITIES · SYSTEMD / KUBERNETES

Cron to Systemd & Kubernetes,
production-ready timers & manifests.

Translate 5-field cron expressions into systemd .timer / .service units, Kubernetes CronJob YAML, and GitHub Actions workflows—or convert systemd OnCalendar back to cron locally.

Presets
Parsed Schedule & OnCalendarMon *-*-* 9:0:00 UTCEvery Mon at 09:00 UTC
Unit & Container Parameters
100% client-side · Zero server uploads

Ready: Every Mon at 09:00 UTC

SYNTAX MATRIX

Cron vs. Systemd OnCalendar vs. Kubernetes Schedule comparison.

Schedule IntentCronSystemd OnCalendarKubernetes YAML
Every Monday at 9 AM0 9 * * 1Mon *-*-* 9:0:00 UTC"0 9 * * 1"
Every day at midnight0 0 * * **-*-* 0:0:00 UTC"0 0 * * *"
Hourly on the hour0 * * * **-*-* *:0:00 UTC"0 * * * *"
Every 15 minutes*/15 * * * **-*-* *:0/15:00 UTC"*/15 * * * *"
1st of month at 3 AM0 3 1 * **-*-1 3:0:00 UTC"0 3 1 * *"

100% Local Infrastructure Safety

Internal script paths, container registries, and job names stay strictly inside your browser tab.

Frequently Asked Questions

How do systemd timers compare to traditional crontab entries?

Systemd timers offer native journald logging, explicit failure tracking, dependency ordering (such as waiting for network-online.target), RandomizedDelaySec jitter, and Persistent=true to catch up missed runs after downtime.

How does the systemd OnCalendar format work?

The OnCalendar syntax expresses calendar events in DayOfWeek Year-Month-Day Hour:Minute:Second format (e.g., Mon *-*-* 9:0:00 UTC). Wildcards (*) represent all units, ranges use .. (Mon..Fri), and steps use / (0/15).

Why does Kubernetes require cron schedule strings to be quoted?

In Kubernetes YAML manifests, unquoted cron expressions starting with asterisks (* * * * *) are parsed as YAML aliases and fail validation. Quoting schedules preserves the exact string.

How do I install the generated systemd timer and service?

Place the .service and .timer files in /etc/systemd/system/, run sudo systemctl daemon-reload, and enable the timer with sudo systemctl enable --now <task>.timer. Use systemctl list-timers to verify the next run.

Does this tool transmit or log any server configurations?

Never. All schedule parsing, OnCalendar translation, and manifest rendering run 100% locally in your browser.