Users are unable to access the Harbor UI after deployment. A browser attempt results in an ERR_CONNECTION_REFUSED. Further investigation shows:
kubectl get httpproxy -n svc-harbor-domain-UUID

This issue occurs because the harbor-data-values.yaml file contains malformed certificate formatting or incorrect YAML indentation. The UI validator may not catch these specific syntax errors, allowing an invalid configuration to be applied.
To resolve this issue, correct the formatting in the Harbor Supervisor Service configuration:
Workload Management > Services.Actions > Manage Service.tlsCertificate: block.tls.crt:) must be indented with two spaces.-----BEGIN CERTIFICATE-----) must be indented with four spaces.Example:
tls.crt: |
-----BEGIN CERTIFICATE-----
MIIFKzCCBBOgAwIBAgITFQAAk6CGmpMuJlfXDgABAACToDANBgkqhkiG9w0BAQ0F
ADBZMRUwEwYKCZImiZPyLGQBGRYFbG9jYWwxHDAaBgoJkiaJk/IsZAEZFgxtczFz
....
A1UECBMMTm9ydGggRGFrb3RhMQ4wDAYDVQQHEwVGYXJnbzENMAsGA1UEChMERklC
VDELMAkGA1UECxMCSVQxIjAgBgNVBAMTGUhhcmJvci5tczFzdGludGVyYmsubG9j
-----END CERTIFICATE-----