minimizing debug logs related to the backoff interval

[shawkins]

Description

Removing the log in the calculator and relying on surrounding logs. If needed we can add a debug / trace log to the Utils.schedule method.

cc @csviri

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[manusa]

Since the log entry was added by @metacosm, adding him as a reviewer.

I don't mind removing the log entry, or maybe just switching it to a trace (I'd prefer this option). However, I don't think this addresses the issue @csviri was reporting in yesterday's internal meeting.

To note, there are logs in the dependent classes:

kubernetes-client/kubernetes-client-api/src/main/java/io/fabric8/kubernetes/client/http/StandardHttpClient.java

Line 145 in 1020516

LOG.debug("HTTP operation on url: {} should be retried as the response code was {}, retrying after {} millis",

• Changes in this PR to the AbstractWatchManager to include info about the reconnection

• Missing in Reflector, but would likely duplicate what was added to the AbstractWatchManager in this class

[csviri]

Little late but LGTM :)