Skip to main content

Work, WorkPlacement Status and Events

A Work represents the output of a workflow. Each Work is scheduled to one or more Destinations. Its progress is tracked through conditions.

A WorkPlacement ties part of a Work to a specific Destination. Its status shows whether the documents were written successfully.

Work Conditions​

Works expose the following conditions:

  • ScheduleSucceeded – set to True once all WorkPlacements have been created. If Kratix cannot find matching Destinations this condition is False with reason UnscheduledWorkloads.
  • Ready – set to True when every WorkPlacement has been written to its State Store.

Each condition's observedGeneration is the Work generation it was set for.

Example output from kubectl get work <name> -o yaml once all WorkPlacements are written:

status:
conditions:
- lastTransitionTime: "2026-10-15T11:25:21Z"
message: All workplacements scheduled successfully
observedGeneration: 1
reason: AllWorkplacementsScheduled
status: "True"
type: ScheduleSucceeded
- lastTransitionTime: "2026-10-15T11:25:36Z"
message: Ready
observedGeneration: 1
reason: AllWorkplacementsWritten
status: "True"
type: Ready

While the WorkPlacements are scheduled but not yet written:

- lastTransitionTime: "2026-10-15T11:25:55Z"
message: Pending
observedGeneration: 1
reason: WaitingForWorkplacementsToBeWritten
status: "False"
type: Ready

When a WorkPlacement fails to write:

status:
conditions:
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: All workplacements scheduled successfully
observedGeneration: 1
reason: AllWorkplacementsScheduled
status: "True"
type: ScheduleSucceeded
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: Failing
observedGeneration: 1
reason: WorkplacementsFailing
status: "False"
type: Ready

When no Destination matches:

status:
conditions:
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: 'No matching destination found for workloadGroups: [5058f1af8388633f609cadb75a75dc9d]'
observedGeneration: 1
reason: UnscheduledWorkloads
status: "False"
type: ScheduleSucceeded
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: Pending
observedGeneration: 1
reason: UnscheduledWorkloads
status: "False"
type: Ready

WorkPlacement Conditions​

WorkPlacements expose the following conditions:

  • ScheduleSucceeded – True when the WorkPlacement has been scheduled to a matching Destination.
  • WriteSucceeded – indicates the documents were written to the State Store backing the Destination.
  • Ready – True when both ScheduleSucceeded and WriteSucceeded are true.

Example output from kubectl get workplacement <name> -o yaml:

status:
conditions:
- lastTransitionTime: "2025-06-23T14:03:20Z"
message: Scheduled to correct Destination
observedGeneration: 1
reason: ScheduledToDestination
status: "True"
type: ScheduleSucceeded
- lastTransitionTime: "2025-06-23T14:03:20Z"
message: Ready
observedGeneration: 1
reason: WorkloadsWrittenToTargetDestination
status: "True"
type: Ready
- lastTransitionTime: "2025-06-23T14:03:20Z"
message: Workloads written to State Store
observedGeneration: 1
reason: WorkloadsWrittenToStateStore
status: "True"
type: WriteSucceeded

Destination not ready​

Kratix does not write to a Destination whose Ready condition is False:

status:
conditions:
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: 'Destination "worker-1" is not ready: GitStateStore/default: not ready'
observedGeneration: 1
reason: DestinationNotReady
status: "False"
type: WriteSucceeded
- lastTransitionTime: "2026-10-15T11:24:49Z"
message: Failing
observedGeneration: 1
reason: DestinationNotReady
status: "False"
type: Ready

Events​

Events on Works and WorkPlacements highlight scheduling progress and any issues writing to Destinations.

Run kubectl describe to inspect Works and Workplacements events:

kubectl describe work <name>
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning DestinationSelectorMismatch 4s (x2 over 5s) Scheduler Target destination no longer matches destinationSelectors for workloadGroups:

kubectl describe workplacement <name>
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal WorkloadsWrittenToStateStore 2m23s WorkPlacementController successfully written to Destination: worker-1 with versionID:...

Successful events will be of type Normal whereas errors will be published as Warning events.