NooBaaAccount does not reconcile when its credentials Secret is deleted

[aayushchouhan09]

Environment info

• NooBaa Operator Version: VERSION
• Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify

Actual behavior

1. Deleting the credentials Secret noobaa-account-<name> does not trigger NooBaaAccount reconcile. The controller only watches NooBaaAccount (GenerationChangedPredicate/ labels / finalizers) and does not watch the owned Secret. Phase can stay Ready with the Secret missing until the next CR reconcile (e.g. a spec patch).

Expected behavior

1. When the credentials Secret is deleted, the NooBaaAccount is reconciled promptly and the Secret is recreated (or phase reflects that credentials are missing).

Steps to reproduce

1. Create a NooBaaAccount; wait until Ready and confirm Secret noobaa-account-<name> exists.
2. Delete that Secret only (do not change the NooBaaAccount CR).
3. Observe: no reconcile; CR stays Ready; Secret remains missing until a CR change forces reconcile.

More information - Screenshots / Logs / Other output

[coderabbitai]

🔗 Related PRs

#2062 - fix: ensure NooBaaAccount credentials Secret exists before Ready [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[aayushchouhan09]

Gap from the bug fix PR