Jamil bfca4e8411 fix(portal): Use threshold-based logging for cluster errors (#9342) ...

We periodically fetch a list of all `RUNNING` VMs in GCP and then try to
connect to them for clustering. However, during deploys, it's expected
that we won't be able to connect to new VMs until they are fully up. The
fetch doesn't take health checks into account, so we need a
threshold-based error logging.

To address this, we do the following:

- We only log an error when failing to connect to nodes if we are
currently below the threshold for each of the `api`, `domain`, and `web`
node counts
- We silence node timeout errors, as these will happen during deploys

2025-06-01 15:53:38 +00:00

..

api

refactor(portal): remove created_by_<identity/actor> columns (#9306)

2025-05-30 21:06:35 +00:00

domain

fix(portal): Use threshold-based logging for cluster errors (#9342)

2025-06-01 15:53:38 +00:00

web

fix(portal): Use account param for autoredirect (#9304)

2025-05-30 21:23:25 +00:00