headyj

@mminisha did you finally fixed your issue about the graph? I have exactly the same issue, the graph is not moving and I cannot see the transactions.

indeed this is resolving the issue, thank your for your workaround @CGeorg-ci ! Anyway I think you're right by saying that this is still an annoying bug that should be...

Thank you for your answer No it didn't, I first thought that this was due to CPU/memory limits (as suggested in another issue), but I already tried to increase it:...

Same problem with the `velero:main` image, no error on the logs, no restarts. The velero pod just stop outputting logs regarding the backup, acting like it was finished: Last logs...

Yes indeed it's logging `Node ip-[....].compute.internal is not suitable for removal - cpu utilization too big (0.822704)` for all of the nodes, but I was wondering how it is possible...

I don't know how CPU usage is calculated, but it seems to be way off the reality. According the AWS monitoring dashboard, CPU usage is under 10% for an hour,...

Any news on that? because the data source does not fulfill this request. @radkomateusz I don't think this is a problem, as many providers are doing the same thing. For...

Yep sorry @radkomateusz, I just wanted to mention @armsnyder obviously ;) @armsnyder is someone working on this feature? it was opened a year ago now. If not I can do...

I have exactly the same issue. Even if many of my nodes are under disk pressure, lots of pods cannot be scheduled, but still the autoscaler is not scaling up:...

I just wanted to add that even if https://github.com/argoproj/argo-helm/issues/1309 has been closed that I still have the issue with latest 4.10.5 version: ``` rpc error: code = Unknown desc =...