Cron Reference

Cron Expression 0 18 * * 1-5 Weekdays at 6PM Kubernetes CronJob (2026)

Cron expression 0 18 * * 1-5 means At 6:00 PM, Monday through Friday.

Cron expression 0 18 * * 1-5 weekdays at 6PM for Kubernetes CronJob in 2026. Configure end-of-day cluster jobs with safe weekday scheduling and operational guardrails.

Cron Expression

0 18 * * 1-5

0Minute

18Hour

*Day

*Month

1-5Weekday

Common use cases

Weekday 6 PM reconciliation jobs in Kubernetes
Business-day exports that should skip weekends
End-of-day analytics snapshots in clusters
Weekday-only processing for partner or finance workflows

How to use this cron schedule

If your target query is cron expression 0 18 * * 1-5 weekdays at 6pm Kubernetes CronJob, set `spec.schedule: "0 18 * * 1-5"` in your CronJob manifest. This runs Monday through Friday at 6:00 PM according to the scheduler timezone. In 2026, it is a strong fit for end-of-day workloads that should capture a full business day but avoid weekend compute and alert noise. Examples include reconciliation, data exports, and post-close reporting that teams consume the next morning.

Weekday scheduling in Kubernetes still needs explicit operational controls. Use `concurrencyPolicy` to prevent overlap when one run slows down, and set resource requests high enough for predictable completion under peak data volume. If your cluster supports a `timeZone` field, decide whether the job should follow UTC or a business timezone and record that choice in code review. For weekday-only workflows, clarity about local execution matters more than the cron syntax itself. Emit structured logs, run IDs, and output counts so missing next-morning reports can be traced quickly without guesswork.

A practical 2026 rollout is staged automation: run validation before 6 PM, execute the main export at 6 PM, and publish a completion status after results land. This reduces blast radius and shortens incident response when one part of the workflow fails. Monitor last-success age, duration, and failure streaks rather than only watching pod creation. If weekend support becomes necessary later, add a dedicated weekend CronJob instead of overloading this weekday schedule with conditionals. Use this page as the Kubernetes reference for `0 18 * * 1-5`, then compare related Linux, GitHub Actions, and hourly cron pages as requirements broaden.

Want to customize this schedule?

Open it in the visual builder to tweak the expression interactively.

Open in Builder

Need to monitor this cron job?

Cronhub tracks your scheduled jobs and alerts you if they fail or run late.

Monitor with Cronhub

Platform usage examples

Linux / Unix — crontab

# Edit your crontab
crontab -e

# Add this line to run expression 0 18 * * 1-5 weekdays at 6pm kubernetes cronjob (2026)
0 18 * * 1-5 /usr/bin/php /var/www/html/script.php

# Or run a shell script
0 18 * * 1-5 /home/user/scripts/job.sh >> /var/log/job.log 2>&1

GitHub Actions

# .github/workflows/scheduled.yml
name: Scheduled Job

on:
  schedule:
    - cron: '0 18 * * 1-5'

jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run job
        run: echo "Running expression 0 18 * * 1-5 weekdays at 6pm kubernetes cronjob (2026)"

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-scheduled-job
spec:
  schedule: "0 18 * * 1-5"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: job
            image: my-image:latest
          restartPolicy: OnFailure

Related developer tools

More free tools for engineering workflows that pair with scheduled jobs:

Epoch ConverterConvert Unix timestamps Regex TesterDebug parsing rules

Frequently asked questions

What is the cron expression for expression 0 18 * * 1-5 weekdays at 6pm kubernetes cronjob (2026)?

The cron expression is 0 18 * * 1-5. Cron expression 0 18 * * 1-5 weekdays at 6PM for Kubernetes CronJob in 2026. Configure end-of-day cluster jobs with safe weekday scheduling and operational guardrails.

How do I schedule a cron job to run expression 0 18 * * 1-5 weekdays at 6pm kubernetes cronjob (2026) in Linux?

Open your crontab with "crontab -e" and add a new line: 0 18 * * 1-5 /path/to/your/script.sh — this schedules your script to run expression 0 18 * * 1-5 weekdays at 6pm kubernetes cronjob (2026). Save and exit; the cron daemon picks up the change immediately.

What does the cron expression "0 18 * * 1-5" mean?

Cron expression 0 18 * * 1-5 weekdays at 6PM for Kubernetes CronJob in 2026. Configure end-of-day cluster jobs with safe weekday scheduling and operational guardrails.

Can I use "0 18 * * 1-5" in GitHub Actions?

Yes. In your workflow YAML, set the schedule trigger: on: schedule: - cron: '0 18 * * 1-5'. GitHub Actions uses standard 5-field Unix cron syntax, so this expression works as-is.

Related cron schedules

0 18 * * 1-5Cron Every Weekday at 6 PM 0 18 * * 1-5Cron Every Weekday at 6 PM Meaning (2026)0 18 * * 1-5Cron Expression 0 18 * * 1-5 Meaning 0 18 * * 1-5Cron Expression 0 18 * * 1-5 Weekdays at 6PM GitHub Actions (2026)0 * * * *Cron Expression 0 * * * * Every Hour Kubernetes CronJob (2026)0 8 * * *Cron Every Day at 8 AM