[bug]: Error refused errors generate too many error logs

[slacki123]

Describe the bug

When running the operator for the first time without any connection configuration, we quickly get an overwhelming spam of error connection logs on startup

This also happens if the operator loses connection somewhere in the midst of processing. The number of logs is a bit overwhelming and difficult to work with

To reproduce

1. Create an operator
2. run the operator without any connection config
3. see there is an overwhelming number of logs

OR

1. create an operator and run locally with a proxy to a kubernetes cluster pointing at the correct port kubectl proxy -p 8080
2. let the operator do some processing
3. kill the kubectl proxy -p 8080 command
4. An overwhelming number of logs will be generated

Expected behavior

Perhaps a 1 or 2 second delay between errors when the connection has been refused

Screenshots

Additional Context

No response