CronJob-clarify on the spec fields

Asking for help? Comment out what you need so we can get more information to help you!
In cron job we have 3 specs(specifications)
1st Spec for cron job
2nd Spec for job
3rd Spec for pod

below fields will be part of which part of the specification and why? can someone guide me clarifying this point
completions:
parllelism:
backOffLimit:
activeDeadlineSeconds
successfulJobsHistoryLimit:
failedJobsHistoryLimit:

Cluster information:

Kubernetes version:V1.26
Cloud being used: (put bare-metal if not on a public cloud): killershell

Hello @Vijji_chander, you could run the below to find out more!

kubectl explain job.spec

FIELDS:
activeDeadlineSeconds
Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it;

backoffLimit
Specifies the number of retries before marking this job failed. Defaults to 6

backoffLimitPerIndex
Specifies the limit for the number of retries within an index before marking
this index as failed.

completionMode
completionMode specifies how Pod completions are tracked. It can be
NonIndexed (default) or Indexed.

completions
Specifies the desired number of successfully finished pods the job should be
run with.

manualSelector
manualSelector controls generation of pod labels and pod selectors.

maxFailedIndexes
Specifies the maximal number of failed indexes before marking the Job as
failed, when backoffLimitPerIndex is set.

parallelism
Specifies the maximum desired number of pods the job should run at any given time.

podFailurePolicy
Specifies the policy of handling failed pods.

podReplacementPolicy
podReplacementPolicy specifies when to create replacement Pods.

selector
A label query over pods that should match the pod count. Normally, the
system sets this field for you.

suspend
suspend specifies whether the Job controller should create Pods or not.

template -required-
Describes the pod that will be created when executing a job.

ttlSecondsAfterFinished
ttlSecondsAfterFinished limits the lifetime of a Job that has finished
execution (either Complete or Failed).

kubectl explain cronjob.spec

FIELDS:
concurrencyPolicy
Specifies how to treat concurrent executions of a Job.

failedJobsHistoryLimit
The number of failed finished jobs to retain. Value must be non-negative
integer. Defaults to 1.

jobTemplate -required-
Specifies the job that will be created when executing a CronJob.

schedule -required-
The schedule in Cron format, see cron - Wikipedia.

startingDeadlineSeconds
Optional deadline in seconds for starting the job if it misses scheduled
time for any reason.

successfulJobsHistoryLimit
The number of successful finished jobs to retain. Value must be non-negative

suspend
This flag tells the controller to suspend subsequent executions, it does not
apply to already started executions.

timeZone
The time zone name for the given schedule,