Skip to main content
NetApp Knowledge Base

Unable to Pull Trident Images From registry.k8s.io Due To connection reset by peer Error When Accessing Google Artifact Registry

  1. Last updated
  2. Save as PDF
Views:
14
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
astra
Last Updated:

Applies to

  • Trident (all versions)
  • Image pulls from registry.k8s.io (which redirects to Google Artifact Registry: *.pkg.dev)

Issue

  • Kubernetes nodes are unable to pull Trident container images from registry.k8s.io.
  • The following error is observed in pod events and image pull logs:
Warning  Failed  kubelet  Failed to pull image "registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.13.0":
failed to pull and unpack image "registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.13.0":
failed to do request:
read tcp xx.xxx.xxx.xxx:45070->xxx.xxx.xxx.xx:443: read: connection reset by peer
  • Layer 4 (TCP) connectivity tests (e.g., nc -v registry.k8s.io 443) succeed, but HTTPS/TLS (Layer 7) requests using curl or openssl s_client to us-central1-docker.pkg.dev fail with “connection reset by peer”.

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.