B Example of a Private Registry HA setup Helm chart #
The following example values file illustrates parameters that are required for the minimal Private Registry HA setup.
expose:
ingress:
hosts:
core: core.harbor.domain 1
externalURL: https://core.harbor.domain 2
portal:
replicas: 2 3
core:
replicas: 2 4
jobservice:
replicas: 2 5
registry:
replicas: 2 6
database:
type: external
external: 7
host: "192.168.0.1"
port: "5432"
username: "user"
password: "password"
coreDatabase: "registry"
existingSecret: "" 8
sslmode: "disable" 9
redis:
type: external
external: 10
addr: "192.168.0.2:6379" 11
sentinelMasterSet: "" 12
coreDatabaseIndex: "0" 13
jobserviceDatabaseIndex: "1"
registryDatabaseIndex: "2"
trivyAdapterIndex: "5"
harborDatabaseIndex: "6" 14
cacheLayerDatabaseIndex: "7"15
username: "" 16
password: ""
existingSecret: "" 17
Core service host name in Ingress rule. | |
The external URL for the harbor-core service. | |
Number of replicas to create. Specify two or more. | |
Fill the database connection details in the | |
If using an existing secret, the value must be | |
Accepts one of the following values:
| |
Fill the connection information in the | |
Supports redis and redis+sentinel. | |
The name of the set of Valkey instances to monitor. It must be set to support redis+sentinel. | |
Must be | |
Optional. Defaults to | |
Optional. Defaults to | |
If empty, it is authenticated against the default user. | |
If used, the key must be <REDIS_PASSWORD>. |