Container App Jobs
Memi Lavi
www.memilavi.com
Container App Jobs
• So far we worked with web apps and API
• For this we used regular container apps
• Listen to incoming requests, always running
• Container Apps support also jobs
• Run for finite time and exits
• Called Container App Jobs
Container App Jobs
• Run jobs
• Execute for finite duration and exits
• Great for data processing, machine learning, reporting and more
Job Triggers
• Container Jobs are triggered using the following trigger types:
Manual Job is manually executed by the user
Schedule Job is scheduled using cron expression
Job is triggered by events such as message arriving in
Event queue. Based on KEDA scaler
Cron Expressions
• Widely used to schedule operations
• Formats can vary between vendors
• Specify minute, hour, day of month, month, and day of week
• Each element is indicated as a * (always), number, expression
• Spaces between elements
Cron Expressions Examples
0 0 * * * Every day at 00:00
*/5 * * * * Every five minutes
0 * 4 * * At the beginning of every hour on the 4th of every month
30 5 * * 1 Every Monday at 5:30am
Container App Jobs Deployment
• Share the same environment with the regular Container Apps
• Use the same network and logging
• Deployment is similar to regular container apps
Container App Jobs Limitations
• No Revisions
• No Dapr support
• No ingress configuration
• Jobs do not receive incoming traffic