fix(workloadmonitor): keep a bucket not ready until its claim is provisioned

A bucket WorkloadMonitor has no pods and minReplicas 0, so it stayed
operational, and the Bucket app stayed Ready, while its BucketClaim was
never provisioned. A tenant whose nearest S3 ancestor runs no SeaweedFS
gets a claim for a bucket class that does not exist, and the dashboard
showed a ready bucket that was never created.

Assisted-by: LLM
Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com>
This commit is contained in:
Yan Bondarenko committed 2026-11-01 11:42:17 +03:00
1 parent 94ada11eef
commit 9d33037566
3 files changed
+168 -3

No files matched your search

+4
View File
@@ -39,6 +39,10 @@ type WorkloadMonitorSpec struct {
// that is not operational because a DataVolume it selects is not ready.
const WorkloadMonitorReasonDataVolumeNotReady = "DataVolumeNotReady"
// WorkloadMonitorReasonBucketClaimNotReady is the status Reason of a monitor
// that is not operational because a BucketClaim it selects is not provisioned.
const WorkloadMonitorReasonBucketClaimNotReady = "BucketClaimNotReady"
// WorkloadMonitorStatus defines the observed state of WorkloadMonitor
type WorkloadMonitorStatus struct {
// Operational indicates if the workload meets all operational requirements