trinolb keeps hanging when api server is not available #83
Description
tonight we had some issues with the kubeapi server (not available because network issue for ~1-2 min) which is used by trinolb to fetch health state of connected trino clusters (CRs). it seems like there is no timeout / retry configured for that type of request, which leads to trinolb waiting forever (30 min in our case, then i restarted the sts manually) to get an answer of the api server.
important to know may be that were using stackable autoscaler
is there a timeout set for kubeapi server calls?