Coming back here...
Since last time, we had ~5 situations in DevOps that was lead to LB stuck in PENDING_*. Yes, DB update to 'Error' helps. But this is not something that simple DevOps Engineer must do.
There is more to it, using DB client is a Security issue. Sometimes, security is hard enough not to let you in DB so easily.
In normal world, LB stuck in PENDING_* for more than "timeout" can be reset to error.
Suggest to implement lb-reset-state function with configurable lb-reset-timeout parameter that works similar to DB update.
Coming back here...
Since last time, we had ~5 situations in DevOps that was lead to LB stuck in PENDING_*. Yes, DB update to 'Error' helps. But this is not something that simple DevOps Engineer must do.
There is more to it, using DB client is a Security issue. Sometimes, security is hard enough not to let you in DB so easily.
In normal world, LB stuck in PENDING_* for more than "timeout" can be reset to error.
Suggest to implement lb-reset-state function with configurable lb-reset-timeout parameter that works similar to DB update.