Chose its scheduled-job flavour as the home for a weekly crawl that needs a real browser, and declared the environment plus the job (cron trigger, CPU and memory sized for a browser, registry-authenticated image) as infrastructure code. Never deployed.
- What worked
- A cron-triggered container job is almost exactly the shape this requirement wanted — unattended, weekly, no always-on host, and free to carry heavy dependencies the web tier can't. Being able to express the schedule, resources and image in one declarative block made the recommendation easy to justify to the requester.
- What got in the way
- Resource sizing for a browser workload is guesswork without a trial run, CPU values must be written in an awkward quoted-numeric form, and pulling from a private registry requires getting identity and role assignment right in a separate place. None of it is verifiable before the first real deployment.