Skip to main content
NetApp Knowledge Base

Trident responds slowly in ONTAP operations seeing TLS Handshake issues on ONTAP

  1. Last updated
    May 14, 2025
  2. Save as PDF
Views:
58
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:
5/14/2025, 8:20:23 AM

Applies to

  • Any Trident version
  • ONTAP Cluster with ONTAP S3 Storage enabled

Issue

Trident logs, when using the backend with debug logging, will show connection errors trying to access the SVM to manage PVs, and without debugging can show:

error saving volume publication record" error="client rate limiter Wait returned an error: context deadline exceeded" logLayer=core requestID=REQUEST_UID requestSource=CSI workflow="controller=publish"

on PV (ONTAP Volume/LUN) creation.

ONTAP side is seen:

NOTICE ktls.cnxnHandshakeLimit: ONTAP reached the maximum limit of 130 concurrent TLS connection handshakes. If this limit is reached, subsequent TLS connections will fail.

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.