Skip to main content
NetApp Knowledge Base

Syslog gets spammed by kubelet of the Kubernetes nodes

Views:
43
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Kubernetes cluster
  • NetApp Astra Trident

Issue

The kubelet of the kubernetes nodes spams the syslog with traces like the following, related to Trident:

Month Day hh:mm:ss hostname...
kubelet[PID]: IMMDD hh:mm:ss clientconn.go:XXX] parsed scheme: ""
Month Day hh:mm:ss hostname... kubelet[PID]:
IMMDD hh:mm:ss clientconn.go:XXX] scheme "" not registered, fallback to default scheme
Month Day 08:09:28 hostname...
kubelet[2841399]: Immdd hh:mm:ss PID passthrough.go:XX] ccResolverWrapper: sending update to cc:
{[{/var/lib/kubelet/plugins/csi.trident.netapp.io/csi.sock  <nil> 0 <nil>}] <nil> <nil>}
Month DD hh:mm:ss hostname... kubelet[PID]:
IMMDD hh:mm:ss clientconn.go:948] ClientConn switching balancer to "pick_first"
Month DD hh:mm:ss hostname...
kubelet[PID]: IMMDD hh:mm:ss clientconn.go:XXX] blockingPicker: the picked transport is not ready, loop back to
repick

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support