Skip to main content
NetApp Stage KB

How to test connectivity to Trident CSI Controller from a particular Kubernetes node

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

Astra Trident

Description

When only Trident CSI on a particular node fails to update Trident controller due to "connection refused", troubleshooting is required to see if the issue depends on a problem of Kubernetes network layer.

level=warning msg="Could not update Trident controller with node registration, will retry." error="could not log into the Trident CSI Controller: error communicating with Trident CSI Controller; Put \"https://10.100.170.133:34571/trident/v1/node/rhel2\": dial tcp 10.100.170.133:34571: connect: connection refused"

This article explains how to test the connectivity to Trident CSI Controler from each Kubernetes node for troubleshooting.

 

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.
Case Citation
067f9c00-ba3c-4193-b3fa-6c99614622c9