Aleksei Sviridkin 99f3d3b2b7 feat(controller): tag a DataVolume cause with a condition reason ...

WorkloadsReady=False covers different situations: a stopped VM has
no pod and its monitor reports it not operational on purpose, while a
disk whose DataVolume never populates is broken. A consumer that wants
to react to one and not the other had only the message text to go by.

The WorkloadMonitor status gains a Reason next to Message, set to
DataVolumeNotReady by the DataVolume check, and the Application API
carries it into the WorkloadsReady condition in place of the generic
reason whenever a monitor that is not operational names one.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-02 14:02:33 +03:00

..

applicationdefinitions_types.go

docs(api): separate the healthCheckExprs failure modes

2026-09-23 00:05:35 +03:00

groupversion_info.go

Introduce cozystack-controller (#560)

2025-01-09 12:24:51 +01:00

package_types.go

[cozystack-operator] Add Package and PackageSource reconcilers

2025-12-30 11:55:21 +01:00

packagesource_types.go

docs(api): separate the healthCheckExprs failure modes

2026-09-23 00:05:35 +03:00

workload_types.go

Introduce cozystack-controller (#560)

2025-01-09 12:24:51 +01:00

workloadmonitor_types.go

feat(controller): tag a DataVolume cause with a condition reason

2026-10-02 14:02:33 +03:00

zz_generated.deepcopy.go

feat(api): typed waitStrategy/healthCheckExprs for kstatus readiness

2026-07-16 16:45:16 +05:00