(MODULES-11968) Stagger nightly cron to 01:05 UTC

[imaqsood]

Strategy and full slot table: Supported modules: staggered nightly schedule

Summary

Moves the puppetlabs-java_ks nightly workflow from 0 0 * * * to 5 1 * * * (01:05 UTC). Only the cron: line in .github/workflows/nightly.yml changes; workflow_dispatch and the jobs are untouched.

Additional Context

• Root cause: all 40 supported modules start their nightly at 00:00 UTC. That sends about 467 provision_service VM requests at once and hit the GCP FIREWALLS quota on 2026-10-01 (389 provision failures).
• Approach: each module gets its own 15-minute slot between 00:05 and 04:50 UTC. Slots are weighted by VM count, so at most 4 nightlies and 50 VM requests start in any 30 minutes. This module has about 19 VM jobs per night. Slots avoid :00 because GitHub delays top-of-hour schedules the most.
• This PR is part of wave 1, the 12 heaviest modules (about 231 of the 467 VM requests). Wave 2 (the other 28) follows once wave 1 lands.

Related Issues (if any)

• Jira: MODULES-11968
• Related: MODULES-11966 (CAT cleanup of leaked firewall rules), MODULES-11965 (provision retry; land this wave before or with it)

Checklist

• 🟢 Spec tests. (Not affected; this PR's ci.yml run covers it)
• 🟢 Acceptance tests. (The nightly itself only runs on schedule; check the first run after merge starts at 01:05 UTC)
• Manually verified: exactly one cron line changed (plus the one .sync.yml line for managed modules). Both files parse with ruby -ryaml, and the parsed on.schedule[0].cron equals 5 1 * * *.

🤖 Generated with Claude Code

[bastelfreak]

Aren't you missing the .sync.yml entry?

[imaqsood]

Yes, thanks. I added cron: '5 1 * * *' under .github/workflows/nightly.yml in .sync.yml, matching the workflow (9cf0d97).