Package-level declarations
Types
CronJob represents the configuration of a single cron job.
Builder for CronJobArgs.
CronJobSpec describes how the job execution will look like and when it will actually run.
Builder for CronJobSpecArgs.
CronJobSpec describes how the job execution will look like and when it will actually run.
Builder for CronJobSpecPatchArgs.
CronJobStatus represents the current state of a cron job.
Builder for CronJobStatusArgs.
Job represents the configuration of a single job. This resource waits until its status is ready before registering success for create/update, and populating output properties from the current state of the resource. The following conditions are used to determine whether the resource creation has succeeded or failed:
Builder for JobArgs.
JobCondition describes current state of a job.
Builder for JobConditionArgs.
JobSpec describes how the job execution will look like.
Builder for JobSpecArgs.
JobSpec describes how the job execution will look like.
Builder for JobSpecPatchArgs.
JobStatus represents the current state of a Job.
Builder for JobStatusArgs.
JobTemplateSpec describes the data a Job should have when created from a template
Builder for JobTemplateSpecArgs.
JobTemplateSpec describes the data a Job should have when created from a template
Builder for JobTemplateSpecPatchArgs.
PodFailurePolicy describes how failed pods influence the backoffLimit.
Builder for PodFailurePolicyArgs.
PodFailurePolicyOnExitCodesRequirement describes the requirement for handling a failed pod based on its container exit codes. In particular, it lookups the .state.terminated.exitCode for each app container and init container status, represented by the .status.containerStatuses and .status.initContainerStatuses fields in the Pod status, respectively. Containers completed with success (exit code 0) are excluded from the requirement check.
PodFailurePolicyOnExitCodesRequirement describes the requirement for handling a failed pod based on its container exit codes. In particular, it lookups the .state.terminated.exitCode for each app container and init container status, represented by the .status.containerStatuses and .status.initContainerStatuses fields in the Pod status, respectively. Containers completed with success (exit code 0) are excluded from the requirement check.
PodFailurePolicyOnPodConditionsPattern describes a pattern for matching an actual pod condition type.
PodFailurePolicyOnPodConditionsPattern describes a pattern for matching an actual pod condition type.
PodFailurePolicy describes how failed pods influence the backoffLimit.
Builder for PodFailurePolicyPatchArgs.
PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.
Builder for PodFailurePolicyRuleArgs.
PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.
Builder for PodFailurePolicyRulePatchArgs.
UncountedTerminatedPods holds UIDs of Pods that have terminated but haven't been accounted in Job status counters.
Builder for UncountedTerminatedPodsArgs.