Skip to main content
NetApp Knowledge Base

Syslog gets spammed by kubelet of the Kubernetes nodes

  1. Last updated
  2. Save as PDF
Views:
333
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

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.