In v2.16, we've added a new flag to entirely disable Zync. When this flag is set to 'false', the operator will remove all Zync resources, including the Zync secret. However, a newly introduced 'watch-by' logic checks for the existence of all 3scale secrets. This creates a conflict that results in the operator's 'Available' status being set to 'false'.

 "conditions": [
     {
         "lastTransitionTime": "2025-10-02T07:12:27Z",
         "message": "The following secret(s) could not be found: zync",
         "reason": "MissingWatchedSecrets",
         "status": "False",
         "type": "Available"
     }
 ],

We also calculate the status based on the availability of the default routes, which also returns false if zync is disbaled