Optional Readonly active- If unset, then there is no deadline.
Optional Readonly automountIndicates whether a service account token should be automatically mounted.
Optional Readonly backoffSpecifies the number of retries before marking this job failed.
- If not set, system defaults to 6.
Optional Readonly concurrencySpecifies the concurrency policy for the job.
ConcurrencyPolicy.Forbid
Optional Readonly containersList of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod.
You can add additionnal containers using podSpec.addContainer()
- No containers. Note that a pod spec must include at least one container.
Optional Readonly dnsDNS settings for the pod.
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
policy: DnsPolicy.CLUSTER_FIRST
hostnameAsFQDN: false
Optional Readonly dockerA secret containing docker credentials for authenticating to a registry.
- No auth. Images are assumed to be publicly available.
Optional Readonly failedSpecifies the number of failed jobs history retained. This would retain the Job and the associated Pod resource and can be useful for debugging.
1
Optional Readonly hostHostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod's hosts file.
io.k8s.api.core.v1.HostAlias
Optional Readonly hostHost network for the pod.
false
Readonly imageOptional Readonly initList of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion.
Init containers cannot currently be added ,removed or updated.
Optional Readonly isolateIsolates the pod. This will prevent any ingress or egress connections to / from this pod.
You can however allow explicit connections post instantiation by using the .connections property.
false
Optional Readonly metadataMetadata that all persisted resources must have, which includes all objects users must create.
Optional Readonly podThe pod metadata of this workload.
Optional Readonly restartRestart policy for all containers within the pod.
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
RestartPolicy.ALWAYS
Readonly scheduleOptional Readonly securitySecurityContext holds pod-level security attributes and common container settings.
fsGroupChangePolicy: FsGroupChangePolicy.FsGroupChangePolicy.ALWAYS
ensureNonRoot: true
Optional Readonly selectAutomatically allocates a pod label selector for this workload and add it to the pod metadata. This ensures this workload manages pods created by its pod template.
true
Optional Readonly serviceA service account provides an identity for processes that run in a Pod.
When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default).
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
- No service account.
Optional Readonly sourceOptional Readonly spreadAutomatically spread pods across hostname and zones.
Optional Readonly startingKubernetes attempts to start cron jobs at its schedule time, but this is not guaranteed. This deadline specifies how much time can pass after a schedule point, for which kubernetes can still start the job. For example, if this is set to 100 seconds, kubernetes is allowed to start the job at a maximum 100 seconds after the scheduled time.
Note that the Kubernetes CronJobController checks for things every 10 seconds, for this reason, a deadline below 10 seconds is not allowed, as it may cause your job to never be scheduled.
In addition, kubernetes will stop scheduling jobs if more than 100 schedules were missed (for any reason). This property also controls what time interval should kubernetes consider when counting for missed schedules.
For example, suppose a CronJob is set to schedule a new Job every one minute beginning at 08:30:00,
and its startingDeadline field is not set. If the CronJob controller happens to be down from 08:29:00 to 10:21:00,
the job will not start as the number of missed jobs which missed their schedule is greater than 100.
However, if startingDeadline is set to 200 seconds, kubernetes will only count 3 missed schedules, and thus
start a new execution at 10:22:00.
Duration.seconds(10)
Optional Readonly successfulSpecifies the number of successful jobs history retained. This would retain the Job and the associated Pod resource and can be useful for debugging.
3
Optional Readonly suspendSpecifies if the cron job should be suspended. Only applies to future executions, current ones are remained untouched.
false
Readonly targetOptional Readonly terminationGrace period until the pod is terminated
Duration.seconds(30)
Optional Readonly timeSpecifies the timezone for the job. This helps aligining the schedule to follow the specified timezone.
https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for list of valid timezone values.
- Timezone of kube-controller-manager process.
Optional Readonly ttlLimits the lifetime of a Job that has finished execution (either Complete
or Failed). If this field is set, after the Job finishes, it is eligible to
be automatically deleted. When the Job is being deleted, its lifecycle
guarantees (e.g. finalizers) will be honored. If this field is set to zero,
the Job becomes eligible to be deleted immediately after it finishes. This
field is alpha-level and is only honored by servers that enable the
TTLAfterFinished feature.
- If this field is unset, the Job won't be automatically deleted.
Optional Readonly volumesList of volumes that can be mounted by containers belonging to the pod.
You can also add volumes later using podSpec.addVolume()
Generated using TypeDoc
Specifies the duration the job may be active before the system tries to terminate it.