When Harbor is deployed as a Supervisor service in a vSphere with Tanzu environment, users may need to configure a proxy server to allow Harbor components (such as Core, Jobservice, and Trivy) to access external registries or download vulnerability databases.
To implement proxy settings on the Harbor Supervisor service, you must update the service specification via the vSphere Client. Do not edit the Harbor secret directly from the CLI.
Add the following configuration block to your data-values.yaml or the service specification in the vSphere UI to define the proxy settings for Harbor components:
#! The http/https network proxy for core, exporter, jobservice, trivy
proxy:
httpProxy: ""
httpsProxy: ""
noProxy: 127.0.0.1,localhost,.local,.internal
If your proxy server requires a certificate for the connection, you must render your certificate into an in-place secret and set the secret name in the configuration.
ca.crt which holds the certificate data.#! The custom ca bundle secret, the secret must contain key named "ca.crt"
#! which will be injected into the trust store for core, jobservice, registry, trivy components
caBundleSecretName: <your-secret-name>