CronJobs

Use a Kubernetes CronJob when you want a batch workload to run on a schedule.

Typical examples include nightly data refreshes, periodic evaluation jobs, cleanup tasks, health reports, and scheduled inference preparation work.

Choose a workflow

Workflow	Best for	Current RemoteGPU support
Console	Inspecting the namespace and related pods or events	Console support for creating and managing CronJob resources is not available yet
kubectl	Professional operators who already manage scheduled work with Kubernetes manifests	Supported today with namespace kubeconfig, API key auth, and admission policy checks

When to use a cronjob

Use case	Why CronJob fits
Run work on a schedule	Kubernetes creates jobs from a cron-style schedule
Keep batch logic declarative	The schedule and job template live in version-controlled manifests
Trigger recurring namespace maintenance	Cleanup, sync, and report generation fit well
Reuse normal job semantics	Each scheduled run becomes a standard Kubernetes Job

If you only need a one-time execution, use a Job instead.

Supported cronjob profile

Area	Supported behavior
Resource type	batch/v1 CronJob
Access path	kubectl with namespace kubeconfig and a Kubernetes exec API key
Schedule format	Standard Kubernetes cron schedule syntax
Job template policy	The embedded job template must pass the same SKU and admission rules as other workloads
Namespace model	The cronjob and the jobs it creates stay inside the same namespace boundary

Create a cronjob

RemoteGPU does not yet provide a dedicated console flow for creating or editing CronJob resources.

Use the console for namespace setup, kubeconfig download, and namespace inspection, then create the scheduled workload with kubectl.

Operating cronjobs on RemoteGPU

Topic	Guidance
Resource sizing	The job template inside the cronjob should carry the same SKU labeling discipline as other workloads
Concurrency	Set concurrencyPolicy intentionally so overlapping runs do not surprise you
Job history	Set success and failure history limits so completed jobs do not accumulate indefinitely
Public exposure	CronJobs are batch resources; they do not replace the deployment-service-ingress model used for public HTTP apps

What you can do from the console today

The console is still useful even when the cronjob itself is created with kubectl:

• create the namespace
• download namespace kubeconfig
• inspect pods, events, and logs created by scheduled runs
• inspect related services or ingresses in the same namespace

Read next

• Read Jobs for one-off batch work.
• Read Deployments for long-running services.
• Read Kubernetes overview for the full access model.