5 ms·
Do you capture all of your job code in a single image and reference execution paths on container startup per job? Or, are you building an image per job?
by djboz 3y ago
Do you capture all of your job code in a single image and reference execution paths on container startup per job? Or, are you building an image per job?
- nickjj 3y agoThe jobs all run curl commands to a specific API endpoint with a specific bearer token. Those tokens are loaded through an env through SealedSecrets. They all use the public curl image where I override the command in the Kubernetes cron job definition. The job container itself starts almost instantly since there's no app to boot. If I had a case you're describing I would use the main app's image and run a specific command, in this case I'm assuming if there's not an API endpoint it would be some callable script that lives in your app's code / image.