Garbage collection times out at 30secs

[imilchev]

Regardless of what the value of the --timeout parameter is for the GC command it would always fail at 30sec. This timeout is coming from inside the scan API. I suppose the scan API's upstream client has a 30sec timeout. Since I have a space with 2.5k assets, I cannot do GC now because I guess such a request would take >30sec

[czunker]

Is this still valid? Do you see errors in your logs?

[imilchev]

It is. We ran into this with Patrick last week. However, the issue is not in the operator but in the Mondoo client. The problem is that the backend client we use in the Mondoo client has a 30s timeout, which is not configurable. If we want to fix that, we need to adjust the client

[czunker]

Sounds like two separate problems to me:

• configurable operator timeout vs. fixed client timeout
• Why does it take so long to delete the assets?