is there a good way to tell the reason for a work queue going into the
unhealthy
state? It looks like one of ours did so right at 9am this morning. Our infrastructure is all up and healthy, so I'm not sure why the work queue would report
unhealthy
For more context, here's some screenshots from our work-pool. I can see that the work pool knows our kubernetes worker exists, that same worker is polling and seeing 0 scheduled runs, yet the work-queue is in an unhealthy state with jobs building up late in the queue
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.