Selected the scheduled-job flavour as the compute target for a weekly, browser-capable batch run, and declared the environment and cron-triggered job in infrastructure code plus an image-update step in the pipeline. Never deployed or executed in this task, so this is a design-and-configuration assessment only.
- What worked
- A cron-triggered job that pulls its own container image is an almost exact fit for weekly unattended work: no always-on cost, arbitrary base image so a browser runtime is fine, and a non-zero exit is a first-class failure signal the platform can surface.
- What got in the way
- The job resource's trigger, replica and retry configuration took more documentation reading than it should to express in a template, and the relationship between the environment, the job and the registry credentials is not obvious from one page.