You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing quay 3.9.0 via the operator, it didn't take long to find my k8s cluster going crazy every 6h. I'm apparently hitting my full 40GbE line speed according to Grafana, and I have sustained 500MB/s disk RW. I run rook-ceph in-cluster, FYI. Also, it looks like each clair-app, of which there are two, does their own update leading to two spikes of activity, back to back.
I tried to turn down the update period from 6h to 10d (golang doesn't support the "d" suffix 😢) but found that the YAML isn't merged. When I set
---
matcher:
period: 240h
I ended up with a broken config:
{"level":"error","component":"main","error":"service initialization failed: failed to initialize matcher: failed to create ConnPool: failed to connect to `host=/tmp user=nobody database=`: dial error (dial unix /tmp/.s.PGSQL.5432: connect: no such file or directory)","time":"2023-09-05T13:05:08Z","message":"fatal error"}
After installing quay 3.9.0 via the operator, it didn't take long to find my k8s cluster going crazy every 6h. I'm apparently hitting my full 40GbE line speed according to Grafana, and I have sustained 500MB/s disk RW. I run rook-ceph in-cluster, FYI. Also, it looks like each clair-app, of which there are two, does their own update leading to two spikes of activity, back to back.
I tried to turn down the update period from 6h to 10d (golang doesn't support the "d" suffix 😢) but found that the YAML isn't merged. When I set
I ended up with a broken config:
Attempting to specify the generated fields led to a different error:
Specified config:
The text was updated successfully, but these errors were encountered: