Create a Job
Deploy batch tasks and scheduled operations in minutes.
Prerequisites
Before creating a job, ensure you have:
- A project created in your organization
- A Docker image ready to deploy
- (Optional) A Docker registry configured for private images
Step-by-Step Guide
1. Navigate to Jobs
- Select your project from the project switcher
- Click Jobs in the left sidebar
- Click Create Job
2. Choose Job Type
Select the type of job you want to create:
| Type | Description | Use Case |
|---|---|---|
| Job | Runs once immediately | Migrations, one-time scripts, data imports |
| CronJob | Runs on a schedule | Backups, reports, periodic data processing |
3. Basic Configuration
Job Name
Enter a unique name for your job. This name is used for:
- Identification in the jobs list
- Log filtering
- Execution tracking
Valid: data-processor, backup-job, nightly-report
Invalid: Data Processor, backup_job, nightly.report
Use lowercase letters, numbers, and hyphens. Start with a letter.
Group (Optional)
Enter an optional group name to visually bundle related jobs in the list. Jobs sharing a group are folded into a single collapsible row.
- Free text, up to 63 characters.
- Fixed at creation — cannot be changed later.
Docker Image
Specify the Docker image containing your job script:
| Format | Example |
|---|---|
| Docker Hub | python:3.12-slim |
| GitHub Registry | ghcr.io/org/my-job:v1.0 |
| Custom Registry | registry.example.com/job:latest |
For private registries, configure your registry credentials first.
Container Command (Optional)
Override the command that runs in the container. Enter the complete command as you would type it in a terminal.
python /app/process.py --batch-size=1000
/bin/sh -c 'echo Starting && /app/run.sh'
Leave empty to use the image's default CMD/ENTRYPOINT.
4. Schedule Configuration (CronJob Only)
If you selected CronJob, configure the schedule:
Cron Expression
Use standard cron syntax: minute hour day-of-month month day-of-week
| Expression | Description |
|---|---|
* * * * * | Every minute |
*/5 * * * * | Every 5 minutes |
0 * * * * | Every hour at minute 0 |
0 0 * * * | Daily at midnight |
0 9 * * 1-5 | Weekdays at 9:00 AM |
0 0 1 * * | First day of every month |
Quick presets are available in the form for common schedules.
Timezone
Select the timezone for schedule evaluation (default: UTC).
Use UTC for server-side jobs. Use local timezones for business-hour related tasks.
Concurrency Policy
Control behavior when a new execution is due while a previous run is still active:
| Policy | Behavior | Best For |
|---|---|---|
| Allow | Run new job alongside existing | Independent tasks |
| Forbid | Skip if previous still running | Prevent overlap |
| Replace | Stop running, start new | Always run latest |
History Limits
| Setting | Default | Description |
|---|---|---|
| Successful Jobs History | 3 | Completed executions to keep |
| Failed Jobs History | 1 | Failed executions to keep |
5. Resources & Execution
Compute Class
Select the appropriate compute class for your job:
| Class | CPU:RAM Ratio | Max CPU | Max RAM | Best For |
|---|---|---|---|---|
| Eco | 1:2 | 3 cores | 6 GB | Simple scripts, testing |
| Standard | 1:4 | 15 cores | 58 GB | General batch jobs |
| Production | 1:4 | 6 cores | 28 GB | Critical operations |
| Prod. Compute | 1:2 | 6 cores | 16 GB | CPU-intensive processing |
| Prod. Memory | 1:8 | 6 cores | 58 GB | Data-heavy operations |
| ARM | 1:4 | 8 cores | 32 GB | Cost-optimized processing |
Resource Allocation
Configure resources using sliders:
- CPU: Adjust in millicores (1000 mCPU = 1 core)
- Memory: Automatically calculated based on CPU:RAM ratio
- Ephemeral Storage: Temporary storage for job files (100 MiB - 10 GiB)
Memory is automatically adjusted when you change CPU to maintain the compute class ratio. A 15% tolerance is allowed.
Job Configuration
| Setting | Default | Range | Description |
|---|---|---|---|
| Restart Policy | Never | OnFailure, Never | How to handle container failures |
| Completions | 1 | 1-100 | Total successful runs needed |
| Parallelism | 1 | 1-100 | Maximum concurrent instances |
| Backoff Limit | 3 | 0-100 | Retry attempts before failure |
| Timeout | None | ≥ 1 second | Maximum run duration before the execution is killed |
Restart Policy Options:
- OnFailure: Restart container on failure, retry up to backoff limit
- Never: Don't restart, mark as failed immediately
6. Environment & Files
Environment Variables
Add configuration via environment variables:
- Click Add Variable
- Enter the key and value
- Toggle Secret for sensitive values
| Example Key | Example Value |
|---|---|
DATABASE_URL | postgresql://... |
BATCH_SIZE | 1000 |
LOG_LEVEL | info |
Security Context (Optional)
Configure security restrictions:
| Field | Description |
|---|---|
| Run As User ID | Numeric UID (e.g., 1000) |
| Run As Group ID | Numeric GID (e.g., 1000) |
All jobs benefit from strong isolation by default. Security context is only needed for compliance requirements.
7. Create the Job
- Review your configuration in the summary
- Click Create
- For one-time jobs, execution starts immediately
- For CronJobs, the first execution occurs at the next scheduled time
Job Detail Tabs
One-Time Jobs
| Tab | Description |
|---|---|
| Overview | Status, configuration summary, execution details |
| Configuration | Full job configuration (image, resources, environment) |
| Observability | CPU, memory, and resource usage metrics |
| Logs | Real-time and historical job output |
| Events | Kubernetes events related to the job |
CronJobs
| Tab | Description |
|---|---|
| Overview | Status, schedule, next/last execution, configuration summary |
| Configuration | Full cron job configuration |
| Executions | Run history with status, duration, and logs for each execution |
| Observability | CPU, memory, and resource usage metrics |
| Logs | Real-time and historical job output |
| Events | Kubernetes events related to the cron job |
After Creation
Monitor Execution
- View the job in the Jobs list
- Check the Executions tab for run history (CronJobs)
- View Logs for output
- Check Events for lifecycle events
For CronJobs
- Run Now: Trigger an immediate execution
- Suspend: Pause scheduling
- Resume: Restart scheduling
Example Configurations
Database Backup (CronJob)
| Parameter | Value |
|---|---|
| Name | db-backup |
| Type | CronJob |
| Image | postgres:16-alpine |
| Schedule | 0 2 * * * (Daily at 2 AM) |
| Timezone | UTC |
| Compute Class | Eco |
| CPU | 500 mCPU |
| Memory | 1024 MiB |
| Concurrency | Forbid |
Command:
pg_dump -h $DB_HOST -U $DB_USER -d $DB_NAME | gzip > /backup/$(date +%Y%m%d).sql.gz
Data Processing Job
| Parameter | Value |
|---|---|
| Name | data-processor |
| Type | Job |
| Image | python:3.12-slim |
| Compute Class | Standard |
| CPU | 2000 mCPU |
| Memory | 8192 MiB |
| Completions | 10 |
| Parallelism | 3 |
| Backoff Limit | 2 |
Command:
python /app/process.py --job-index=$JOB_COMPLETION_INDEX
Report Generation (CronJob)
| Parameter | Value |
|---|---|
| Name | weekly-report |
| Type | CronJob |
| Image | node:20-alpine |
| Schedule | 0 8 * * 1 (Mondays at 8 AM) |
| Timezone | Europe/Paris |
| Compute Class | Eco |
| CPU | 1000 mCPU |
| Memory | 2048 MiB |
| Concurrency | Replace |
Troubleshooting
Job Never Starts
- Check the Events tab for scheduling issues
- Verify image exists and is accessible
- For CronJobs, verify schedule expression is valid
Job Fails Immediately
- Check Logs for error messages
- Verify command syntax is correct
- Ensure required environment variables are set
Job Keeps Restarting
- Backoff limit may be too high
- Check if restart policy should be
Never - Look for transient errors in logs
Image Pull Errors
- Verify image name and tag
- Check registry credentials
- Ensure image is built for correct architecture (AMD64 vs ARM)