Further improve agent log levels (avoid spurious errors)

[jkh52]

There have been some improvements in this area:

• chore: reduce annoying error message #317
• agent: reduce noisy error logs when trying to write to a closed network connection #353
• Fix use of closed network connection errors in agent #364

But even after these, I see a few remaining (spurious) errors:

"could not read stream" err="rpc error: code = Unavailable desc = error reading from server: read tcp 10.125.128.150:36690->REDACTED:8132: read: connection reset by peer"

and

"close response failure" err="EOF" ="(MISSING)"

[heku-ard]

+1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[heku-ard]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[heku-ard]

/remove-lifecycle stale