Harbor registryctl - doesn't work properly when internal TLS in the cluster is enabled

[aechegoyan17]

Which image/versions are related to this issue/feature request?

harbor-registryctl:2.11.0
Official Harbor helm chart version 1.15.0

Issue/Feature description

The registryctl throws the following error when using Azure Blob Storage as the storage driver while internalTLS is active within the cluster:

2024-08-01T11:09:03Z [ERROR] [/registryctl/config/config.go:63]: failed to load storage driver, err:Put "https://xxx.blob.core.windows.net/images?restype=container": tls: failed to verify certificate: x509: certificate signed by unknown authority
2024-08-01T11:09:03Z [FATAL] [/registryctl/main.go:102]: Failed to load configurations with error: Put "https://xxx.blob.core.windows.net/images?restype=container": tls: failed to verify certificate: x509: certificate signed by unknown authority

XXX is a redacted value.

It works fine when using plain communication. Any ideas on how to resolve this?

Thank you, regards

[tuananh]

@aechegoyan17 add ca-certificates package?