Description of the problem:
When a source (cluster) does not exist in the Koku API, CMMO attempts to create it via the Koku API but encounters a timeout.
The CMMO HTTP client is configured with a 30-second timeout. Although the source is eventually created, the Koku API takes longer than 30 seconds to complete the request, causing the client to time out.

This issue does not occur in the SaaS environment.

One possible reason is that the Sources API is implemented in Go, while the Koku API is implemented in Python, which may result in slower processing times.

How reproducible:
Deploy the CMMO operator to a new cluster that is not yet registered in the Koku database.

Note: we don't want to change CMMO code.