Harbor fails to add quay.io registry with "Failed to ping endpoint"

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Harbor has been deployed to provide private image registry. 
• Add RedHat's quay.io registry endpoint in Harbor failed and prompt error 'Failed to ping endpoint' when click 'TEST CONNECTION'.
• The Provider is selected as Harbor.
• The 'Access ID' and 'Access Secret' are correct.
• When click 'OK' there are error at the end of HTML responded messages:
  
  The Quay application could not be loaded, which typically indicates an external library could not be loaded
Something went wrong when trying to load Quay! Please report this to [email protected]

Environment

Harbor 2.x

Resolution

To fix the issue:

1. Login Harbor with Admin
2. Click Registries
3. Click NEW ENDPOINT
4. In the prompt of New Registry Endpoint
   • Select Docker Registry in Provider list
   • Input the Name of the registry
   • Endpoint URL is https://quay.io
   • Input correct Access ID and Access Secret
   • Check the option Verify Remote Cert
   • Click OK