Nick Jones

I've run into the same problem: ``` nick@zaphod:..rc/alpine-libreoffice> make run docker run --rm -it --name docker_libreoffice --hostname libreoffice -e PGID=1000 -e PUID=1000 -c 512 -m 2096m -e DISPLAY=unix:0 -v /usr/share/fonts:/usr/share/fonts:ro...

> A bunch of nodes went unresponsive and got tainted and terminated, most pods rescheduled to new nodes eventually. But some ended up in this state where PendingNodeID is pointing...

The bug (CAPO retrying network / subnet / router creation until you hit quota limits) might be trigged by a number of things, but specifically I've hit this recently and...

I've just tested the new release of OCCM on a cluster with 1.30 and have hit this issue as well. For anyone else who is struggling to understand the root...

Similar to OP, various transient network errors result in this state: ``` kubectl get cluster cluster-13ade6bf -n e0881433-b558-4535-bcf5-bb668dd33382 -o jsonpath='{.status.failureMessage}{"\n"}{.status.failureReason}' Failure detected from referenced resource infrastructure.cluster.x-k8s.io/v1beta1, Kind=OpenStackCluster with name "cluster-13ade6bf":...

Nice!! I think it'll also need #189 to really make sense.

@dtenenba Yes, an equivalent feature implemented in Ghostty is the intended outcome from this issue.

This was added a while back: https://github.com/erpalma/throttled/commit/174d6f8cdc08c6c05acb380a7fc225d1ed805860