Stefan Andres
Stefan Andres
Of course it does, that's why we still apply our patch (https://gitlab.com/syseleven/docker-machine/-/tree/concurrent-fip-deletion).
It's rebased now :)
The fix is in the released 2.11.1 release.
> We are even considering writing a controller loop that restarts any device plugin pods stuck in pending for too long We actually do have a workaraound in place for...
Alloy seems to log those errors not, but only on a debug level: ``` monitoring-alloy-metrics-1 alloy ts=2025-08-04T10:08:40.394056755Z level=debug msg="Scrape failed" component_path=/prometheus_operator_objects.feature component_id=prometheus.operator.podmonitors.pod_monitors scrape_pool=podMonitor/kube-system/coredns/0 target=http://10.2.114.110:9153/metrics err="Get \"http://10.2.114.110:9153/metrics\": context deadline exceeded" ```...
That makes sense. I have no good idea how to mitigate this UX issue. I suppose the deployment itself doesn't know what page has actual content and can decide accordingly...
@billabongrob > Setting the cliClientID helped us, FWIW. What did you do on Okta for this? Did you create another Okta app with localhost as callback url or something? It...
This change broke HA and the default setting, see https://github.com/stakater/Reloader/pull/723
That works for me with 0.10.1