K8up Status and Conditions

The following resources support .status.conditions. Conditions are like a multi-state state-machine and give high-level information about the resources.

Each condition also contains a human-readable message that describes the status and reason.

Table 1. Conditions for `Schedule`
Condition	Reasons	Description
`Ready`	Ready	The jobs have been created and added to the cron scheduler.
	Failed	The jobs could not be added to the cron scheduler.
	CreationFailed	Dependent resources could not be created.
	UpdateFailed	Dependent resources could not be updated.
	DeletionFailed	Dependent resources could not be deleted.

Table 2. Conditions for `Archive`, `Backup`, `Check`, `Prune`, `Restore`
Condition	Reasons	Description
`Ready`	Ready	All dependent resource are successfully created, the resource is ready for its main function.
`Ready`	CreationFailed	Dependent resources could not be created.
`Progressing`	Started	This is given when the resource is in the process of doing its main function. This condition is true after reaching Ready condition and reset when it’s finished.
`Progressing`	Finished	The resource is done with its main function. It does not give indication about its success.
`Completed`	Succeeded	The resource could successfully finish its main function.
`Completed`	Failed	A not further categorized failure happened during progression.
`Scrubbed` (does not apply to `Check`)	RetrievalFailed	The resource could not retrieve the resources it’s supposed to clean up.
	DeletionFailed	The resource could not delete one or more resources during cleanup.
	Succeeded	The resource successfully cleaned up old resources.

Table 3. Additional Conditions for `Backup`
Condition	Reasons	Description
`PreBackupPodsReady`	NoPreBackupPodsFound	No PreBackupPod definitions have been found, backups are created without them.
	RetrievalFailed	`PreBackupPod` definitions could not be retrieved from Kubernetes
	Waiting	The `Backup` is waiting for `PreBackupPod` deployments to become ready.
	CreationFailed	`PreBackupPod` deployments could not be created.
	Failed	`PreBackupPod` deployments failed with an unknown error.
	Ready	`PreBackupPod` deployments ready.
	Finished	`PreBackupPod` deployments cleaned up after backup finished.