Notes: The master branch is in heavy development, please use the other stable versions instead. A highly available solution for Harbor based on chart can be found here. And refer to the guide to upgrade the existing deployment.
This repository, including the issues, focuses on deploying Harbor chart via helm. For functionality issues or Harbor questions, please open issues on goharbor/harbor
Introduction
This Helm chart installs Harbor in a Kubernetes cluster. Welcome to contribute to Helm Chart for Harbor.
Prerequisites
Kubernetes cluster 1.20+
Helm v3.2.0+
Installation
Add Helm repository
helm repo add harbor https://helm.goharbor.io
Configure the chart
The following items can be set via --set flag during installation or configured by editing the values.yaml directly (need to download the chart first).
Configure how to expose Harbor service
Ingress: The ingress controller must be installed in the Kubernetes cluster.
Notes: if TLS is disabled, the port must be included in the command when pulling/pushing images. Refer to issue #5291 for details.
ClusterIP: Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster.
NodePort: Exposes the service on each Node’s IP at a static port (the NodePort). You’ll be able to contact the NodePort service, from outside the cluster, by requesting NodeIP:NodePort.
LoadBalancer: Exposes the service externally using a cloud provider’s load balancer.
Gateway APIs: Exposes the service using gateway-api CRDs using HTTPRoute. Requires v1.0.0+
Configure the external URL
The external URL for Harbor core service is used to:
populate the docker/helm commands showed on portal
populate the token service URL returned to docker client
Format: protocol://domain[:port]. Usually:
if service exposed via Ingress, the domain should be the value of expose.ingress.hosts.core
if service exposed via ClusterIP, the domain should be the value of expose.clusterIP.name
if service exposed via NodePort, the domain should be the IP address of one Kubernetes node
if service exposed via LoadBalancer, set the domain as your own domain name and add a CNAME record to map the domain name to the one you got from the cloud provider
If Harbor is deployed behind the proxy, set it as the URL of proxy.
Configure how to persist data
Disable: The data does not survive the termination of a pod.
Persistent Volume Claim(default): A default StorageClass is needed in the Kubernetes cluster to dynamically provision the volumes. Specify another StorageClass in the storageClass or set existingClaim if you already have existing persistent volumes to use.
External Storage(only for images and charts): For images and charts, the external storages are supported: azure, gcs, s3swift and oss.
Configure the other items listed in configuration section
Install the chart
Install the Harbor helm chart with a release name my-release:
helm install my-release harbor/harbor
Uninstallation
To uninstall/delete the my-release deployment:
helm uninstall my-release
Configuration
The following table lists the configurable parameters of the Harbor chart and the default values.
Parameter
Description
Default
Expose
expose.type
How to expose the service: ingress, clusterIP, nodePort or loadBalancer, other values will be ignored and the creation of service will be skipped.
ingress
expose.tls.enabled
Enable TLS or not. Delete the ssl-redirect annotations in expose.ingress.annotations when TLS is disabled and expose.type is ingress. Note: if the expose.type is ingress and TLS is disabled, the port must be included in the command when pulling/pushing images. Refer to https://github.com/goharbor/harbor/issues/5291 for details.
true
expose.tls.certSource
The source of the TLS certificate. Set as auto, secret or none and fill the information in the corresponding section: 1) auto: generate the TLS certificate automatically 2) secret: read the TLS certificate from the specified secret. The TLS certificate can be generated manually or by cert manager 3) none: configure no TLS certificate for the ingress. If the default TLS certificate is configured in the ingress controller, choose this option
auto
expose.tls.auto.commonName
The common name used to generate the certificate, it’s necessary when the type isn’t ingress
expose.tls.secret.secretName
The name of secret which contains keys named: tls.crt - the certificate; tls.key - the private key
expose.ingress.hosts.core
The host of Harbor core service in ingress rule
core.harbor.domain
expose.ingress.controller
The ingress controller type. Currently supports default, gce, alb, f5-bigip and ncp
default
expose.ingress.kubeVersionOverride
Allows the ability to override the kubernetes version used while templating the ingress
expose.ingress.className
Specify the ingressClassName used to implement the Ingress (Kubernetes 1.18+)
expose.ingress.annotations
The annotations used commonly for ingresses
expose.ingress.labels
The labels specific to ingress
{}
expose.clusterIP.name
The name of ClusterIP service
harbor
expose.clusterIP.annotations
The annotations attached to the ClusterIP service
{}
expose.clusterIP.ports.httpPort
The service port Harbor listens on when serving HTTP
80
expose.clusterIP.ports.httpsPort
The service port Harbor listens on when serving HTTPS
443
expose.clusterIP.annotations
The annotations used commonly for clusterIP
expose.clusterIP.labels
The labels specific to clusterIP
{}
expose.nodePort.name
The name of NodePort service
harbor
expose.nodePort.ports.http.port
The service port Harbor listens on when serving HTTP
80
expose.nodePort.ports.http.nodePort
The node port Harbor listens on when serving HTTP
30002
expose.nodePort.ports.https.port
The service port Harbor listens on when serving HTTPS
443
expose.nodePort.ports.https.nodePort
The node port Harbor listens on when serving HTTPS
30003
expose.nodePort.annotations
The annotations used commonly for nodePort
expose.nodePort.labels
The labels specific to nodePort
{}
expose.loadBalancer.name
The name of service
harbor
expose.loadBalancer.IP
The IP of the loadBalancer. It only works when loadBalancer supports assigning IP
""
expose.loadBalancer.ports.httpPort
The service port Harbor listens on when serving HTTP
80
expose.loadBalancer.ports.httpsPort
The service port Harbor listens on when serving HTTPS
30002
expose.loadBalancer.annotations
The annotations attached to the loadBalancer service
{}
expose.loadBalancer.labels
The labels specific to loadBalancer
{}
expose.loadBalancer.sourceRanges
List of IP address ranges to assign to loadBalancerSourceRanges
[]
Internal TLS
internalTLS.enabled
Enable TLS for the components (core, jobservice, portal, registry, trivy)
false
internalTLS.strong_ssl_ciphers
Enable strong ssl ciphers for nginx and portal
false
internalTLS.certSource
Method to provide TLS for the components, options are auto, manual, secret.
auto
internalTLS.trustCa
The content of trust CA, only available when certSource is manual. Note: all the internal certificates of the components must be issued by this CA
internalTLS.core.secretName
The secret name for core component, only available when certSource is secret. The secret must contain keys named: ca.crt - the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA, tls.crt - the content of the TLS cert file, tls.key - the content of the TLS key file.
internalTLS.core.crt
Content of core’s TLS cert file, only available when certSource is manual
internalTLS.core.key
Content of core’s TLS key file, only available when certSource is manual
internalTLS.jobservice.secretName
The secret name for jobservice component, only available when certSource is secret. The secret must contain keys named: ca.crt - the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA, tls.crt - the content of the TLS cert file, tls.key - the content of the TLS key file.
internalTLS.jobservice.crt
Content of jobservice’s TLS cert file, only available when certSource is manual
internalTLS.jobservice.key
Content of jobservice’s TLS key file, only available when certSource is manual
internalTLS.registry.secretName
The secret name for registry component, only available when certSource is secret. The secret must contain keys named: ca.crt - the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA, tls.crt - the content of the TLS cert file, tls.key - the content of the TLS key file.
internalTLS.registry.crt
Content of registry’s TLS cert file, only available when certSource is manual
internalTLS.registry.key
Content of registry’s TLS key file, only available when certSource is manual
internalTLS.portal.secretName
The secret name for portal component, only available when certSource is secret. The secret must contain keys named: ca.crt - the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA, tls.crt - the content of the TLS cert file, tls.key - the content of the TLS key file.
internalTLS.portal.crt
Content of portal’s TLS cert file, only available when certSource is manual
internalTLS.portal.key
Content of portal’s TLS key file, only available when certSource is manual
internalTLS.trivy.secretName
The secret name for trivy component, only available when certSource is secret. The secret must contain keys named: ca.crt - the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA, tls.crt - the content of the TLS cert file, tls.key - the content of the TLS key file.
internalTLS.trivy.crt
Content of trivy’s TLS cert file, only available when certSource is manual
internalTLS.trivy.key
Content of trivy’s TLS key file, only available when certSource is manual
IPFamily
ipFamily.ipv4.enabled
if cluster is ipv4 enabled, all ipv4 related configs will set correspondingly, but currently it only affects the nginx related components
true
ipFamily.ipv6.enabled
if cluster is ipv6 enabled, all ipv6 related configs will set correspondingly, but currently it only affects the nginx related components
true
Persistence
persistence.enabled
Enable the data persistence or not
true
persistence.resourcePolicy
Setting it to keep to avoid removing PVCs during a helm delete operation. Leaving it empty will delete PVCs after the chart deleted. Does not affect PVCs created for internal database and redis components.
Specify the storageClass used to provision the volume. Or the default StorageClass will be used (the default). Set it to - to disable dynamic provisioning
Specify the storageClass used to provision the volume. Or the default StorageClass will be used (the default). Set it to - to disable dynamic provisioning
Use the existing PVC which must be created manually before bound, and specify the subPath if the PVC is shared with other components. If external database is used, the setting will be ignored
Specify the storageClass used to provision the volume. Or the default StorageClass will be used (the default). Set it to - to disable dynamic provisioning. If external database is used, the setting will be ignored
Use the existing PVC which must be created manually before bound, and specify the subPath if the PVC is shared with other components. If external Redis is used, the setting will be ignored
Specify the storageClass used to provision the volume. Or the default StorageClass will be used (the default). Set it to - to disable dynamic provisioning. If external Redis is used, the setting will be ignored
persistence.persistentVolumeClaim.redis.subPath
The sub path used in the volume. If external Redis is used, the setting will be ignored
Specify the storageClass used to provision the volume. Or the default StorageClass will be used (the default). Set it to - to disable dynamic provisioning
The configuration for managing redirects from content backends. For backends which not supported it (such as using minio for s3 storage type), please set it to true to disable redirects. Refer to the guide for more details
false
persistence.imageChartStorage.caBundleSecretName
Specify the caBundleSecretName if the storage service uses a self-signed certificate. The secret must contain keys named ca.crt which will be injected into the trust store of registry’s and containers.
persistence.imageChartStorage.type
The type of storage for images and charts: filesystem, azure, gcs, s3, swift or oss. The type must be filesystem if you want to use persistent volumes for registry. Refer to the guide for more details
filesystem
persistence.imageChartStorage.gcs.existingSecret
An existing secret containing the gcs service account json key. The key must be gcs-key.json.
A boolean to allow the use of workloadidentity in a GKE cluster. To use it, create a kubernetes service account and set the name in the key serviceAccountName of each component, then allow automounting the service account.
false
General
externalURL
The external URL for Harbor core service
https://core.harbor.domain
caBundleSecretName
The custom CA bundle secret name, the secret must contain key named “ca.crt” which will be injected into the trust store for core, jobservice, registry, trivy components.
uaaSecretName
If using external UAA auth which has a self signed cert, you can provide a pre-created secret containing it under the key ca.crt.
imagePullPolicy
The image pull policy
imagePullSecrets
The imagePullSecrets names for all deployments
updateStrategy.type
The update strategy for deployments with persistent volumes(jobservice, registry): RollingUpdate or Recreate. Set it as Recreate when RWM for volumes isn’t supported
RollingUpdate
logLevel
The log level: debug, info, warning, error or fatal
info
harborAdminPassword
The initial password of Harbor admin. Change it from portal after launching Harbor
Harbor12345
existingSecretAdminPassword
The name of secret where admin password can be found.
existingSecretAdminPasswordKey
The name of the key in the secret where to find harbor admin password Harbor
HARBOR_ADMIN_PASSWORD
caSecretName
The name of the secret which contains key named ca.crt. Setting this enables the download link on portal to download the CA certificate when the certificate isn’t generated automatically
secretKey
The key used for encryption. Must be a string of 16 chars
not-a-secure-key
existingSecretSecretKey
An existing secret containing the encoding secretKey
""
proxy.httpProxy
The URL of the HTTP proxy server
proxy.httpsProxy
The URL of the HTTPS proxy server
proxy.noProxy
The URLs that the proxy settings not apply to
127.0.0.1,localhost,.local,.internal
proxy.components
The component list that the proxy settings apply to
core, jobservice, trivy
enableMigrateHelmHook
Run the migration job via helm hook, if it is true, the database migration will be separated from harbor-core, run with a preupgrade job migration-job
false
Nginx (if service exposed via ingress, Nginx will not be used)
The provider for updating project quota(usage), there are 2 options, redis or db. You can set it to be implemented by redis which can improve the performance of high concurrent pushing to the same project, and reduce database connection spikes and occupies. Using redis will bring up some delay for quota usage update for display, so only suggest switch provider to redis if you ran into the db connections spike around the scenario of high concurrent pushing to same project, no improvement for other scenes.
db
core.secret
Secret is used when core server communicates with other components. If a secret key is not specified, Helm will generate one. Must be a string of 16 chars.
core.secretName
Fill the name of a kubernetes secret if you want to use your own TLS certificate and private key for token encryption/decryption. The secret must contain keys named: tls.crt - the certificate and tls.key - the private key. The default key pair will be used if it isn’t set
core.tokenKey
PEM-formatted RSA private key used to sign service tokens. Only used if core.secretName is unset. If set, core.tokenCert MUST also be set.
core.tokenCert
PEM-formatted certificate signed by core.tokenKey used to validate service tokens. Only used if core.secretName is unset. If set, core.tokenKey MUST also be set.
core.xsrfKey
The XSRF key. Will be generated automatically if it isn’t specified
core.priorityClassName
The priority class to run the pod as
core.artifactPullAsyncFlushDuration
The time duration for async update artifact pull_time and repository pull_count
core.gdpr.deleteUser
Enable GDPR compliant user delete
false
core.gdpr.auditLogsCompliant
Enable GDPR compliant for audit logs by changing username to its CRC32 value if that user was deleted from the system
false
core.initContainers
Init containers to be run before the controller’s container starts.
[]
Jobservice
jobservice.image.repository
Repository for jobservice image
goharbor/harbor-jobservice
jobservice.image.tag
Tag for jobservice image
dev
jobservice.replicas
The replica count
1
jobservice.revisionHistoryLimit
The revision history limit
10
jobservice.maxJobWorkers
The max job workers
10
jobservice.jobLoggers
The loggers for jobs: file, database or stdout
[file]
jobservice.loggerSweeperDuration
The jobLogger sweeper duration in days (ignored if jobLoggers is set to stdout)
14
jobservice.notification.webhook_job_max_retry
The maximum retry of webhook sending notifications
The http client timeout value of webhook sending notifications
3
jobservice.registryHttpClientTimeout
The HTTP client timeout (in minutes) for jobservice when communicating with the registry. Only needs to be set if a longer request timeout is required.
30
jobservice.reaper.max_update_hours
the max time to wait for a task to finish, if unfinished after max_update_hours, the task will be mark as error, but the task will continue to run
24
jobservice.reaper.max_dangling_hours
the max time for execution in running state without new task created
Constraints that define how Pods are spread across failure-domains like regions or availability zones
[]
jobservice.podAnnotations
Annotations to add to the jobservice pod
{}
jobservice.priorityClassName
The priority class to run the pod as
jobservice.secret
Secret is used when job service communicates with other components. If a secret key is not specified, Helm will generate one. Must be a string of 16 chars.
jobservice.initContainers
Init containers to be run before the controller’s container starts.
Constraints that define how Pods are spread across failure-domains like regions or availability zones
[]
registry.middleware
Middleware is used to add support for a CDN between backend storage and docker pull recipient. See official docs.
registry.podAnnotations
Annotations to add to the registry pod
{}
registry.priorityClassName
The priority class to run the pod as
registry.secret
Secret is used to secure the upload state from client and registry storage backend. See official docs. If a secret key is not specified, Helm will generate one. Must be a string of 16 chars.
registry.credentials.username
The username that harbor core uses internally to access the registry instance. Together with the registry.credentials.password, a htpasswd is created. This is an alternative to providing registry.credentials.htpasswdString. For more details see official docs.
harbor_registry_user
registry.credentials.password
The password that harbor core uses internally to access the registry instance. Together with the registry.credentials.username, a htpasswd is created. This is an alternative to providing registry.credentials.htpasswdString. For more details see official docs. It is suggested you update this value before installation.
harbor_registry_password
registry.credentials.existingSecret
An existing secret containing the password for accessing the registry instance, which is hosted by htpasswd auth mode. More details see official docs. The key must be REGISTRY_PASSWD
""
registry.credentials.htpasswdString
Login and password in htpasswd string format. Excludes registry.credentials.username and registry.credentials.password. May come in handy when integrating with tools like argocd or flux. This allows the same line to be generated each time the template is rendered, instead of the htpasswd function from helm, which generates different lines each time because of the salt.
undefined
registry.relativeurls
If true, the registry returns relative URLs in Location headers. The client is responsible for resolving the correct URL. Needed if harbor is behind a reverse proxy
false
registry.upload_purging.enabled
If true, enable purge _upload directories
true
registry.upload_purging.age
Remove files in _upload directories which exist for a period of time, default is one week.
168h
registry.upload_purging.interval
The interval of the purge operations
24h
registry.upload_purging.dryrun
If true, enable dryrun for purging _upload
false
registry.initContainers
Init containers to be run before the controller’s container starts.
The resources to allocate for Trivy adapter container
trivy.automountServiceAccountToken
Mount serviceAccountToken?
false
trivy.replicas
The number of Pod replicas
1
trivy.debugMode
The flag to enable Trivy debug mode
false
trivy.vulnType
Comma-separated list of vulnerability types. Possible values os and library.
os,library
trivy.severity
Comma-separated list of severities to be checked
UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL
trivy.ignoreUnfixed
The flag to display only fixed vulnerabilities
false
trivy.insecure
The flag to skip verifying registry certificate
false
trivy.skipUpdate
The flag to disable Trivy DB downloads from GitHub
false
trivy.skipJavaDBUpdate
If the flag is enabled you have to manually download the trivy-java.db file Trivy Java DB and mount it in the /home/scanner/.cache/trivy/java-db/trivy-java.db path
false
trivy.dbRepository
OCI repository(ies) to retrieve the trivy vulnerability database in order of priority
The tracing provider: jaeger or otel. jaeger should be 1.26+
jaeger
trace.sample_rate
Set sample_rate to 1 if you want sampling 100% of trace data; set 0.5 if you want sampling 50% of trace data, and so forth
1
trace.namespace
Namespace used to differentiate different harbor services
trace.attributes
attributes is a key value dict contains user defined attributes used to initialize trace provider
trace.jaeger.endpoint
The endpoint of jaeger
http://hostname:14268/api/traces
trace.jaeger.username
The username of jaeger
trace.jaeger.password
The password of jaeger
trace.jaeger.agent_host
The agent host of jaeger
trace.jaeger.agent_port
The agent port of jaeger
6831
trace.otel.endpoint
The endpoint of otel
hostname:4318
trace.otel.url_path
The URL path of otel
/v1/traces
trace.otel.compression
Whether enable compression or not for otel
false
trace.otel.insecure
Whether establish insecure connection or not for otel
true
trace.otel.timeout
The timeout in seconds of otel
10
Cache
cache.enabled
Enable cache layer or not
false
cache.expireHours
The expire hours of cache layer
24
Harbor Kubernetes Version Compatibility Matrix
The following is a list of the Test Kubernetes versions for each Harbor version. Generally, Harbor supporting Kubernetes version above v1.20+ . However we only test against 3 Kubernetes minor versions for each Harbor minor release.
Helm Chart for Harbor
Notes: The master branch is in heavy development, please use the other stable versions instead. A highly available solution for Harbor based on chart can be found here. And refer to the guide to upgrade the existing deployment.
This repository, including the issues, focuses on deploying Harbor chart via helm. For functionality issues or Harbor questions, please open issues on goharbor/harbor
Introduction
This Helm chart installs Harbor in a Kubernetes cluster. Welcome to contribute to Helm Chart for Harbor.
Prerequisites
Installation
Add Helm repository
Configure the chart
The following items can be set via
--setflag during installation or configured by editing thevalues.yamldirectly (need to download the chart first).Configure how to expose Harbor service
NodeIP:NodePort.Configure the external URL
The external URL for Harbor core service is used to:
Format:
protocol://domain[:port]. Usually:Ingress, thedomainshould be the value ofexpose.ingress.hosts.coreClusterIP, thedomainshould be the value ofexpose.clusterIP.nameNodePort, thedomainshould be the IP address of one Kubernetes nodeLoadBalancer, set thedomainas your own domain name and add a CNAME record to map the domain name to the one you got from the cloud providerIf Harbor is deployed behind the proxy, set it as the URL of proxy.
Configure how to persist data
StorageClassis needed in the Kubernetes cluster to dynamically provision the volumes. Specify another StorageClass in thestorageClassor setexistingClaimif you already have existing persistent volumes to use.azure,gcs,s3swiftandoss.Configure the other items listed in configuration section
Install the chart
Install the Harbor helm chart with a release name
my-release:Uninstallation
To uninstall/delete the
my-releasedeployment:Configuration
The following table lists the configurable parameters of the Harbor chart and the default values.
expose.typeingress,clusterIP,nodePortorloadBalancer, other values will be ignored and the creation of service will be skipped.ingressexpose.tls.enabledssl-redirectannotations inexpose.ingress.annotationswhen TLS is disabled andexpose.typeisingress. Note: if theexpose.typeisingressand TLS is disabled, the port must be included in the command when pulling/pushing images. Refer to https://github.com/goharbor/harbor/issues/5291 for details.trueexpose.tls.certSourceauto,secretornoneand fill the information in the corresponding section: 1) auto: generate the TLS certificate automatically 2) secret: read the TLS certificate from the specified secret. The TLS certificate can be generated manually or by cert manager 3) none: configure no TLS certificate for the ingress. If the default TLS certificate is configured in the ingress controller, choose this optionautoexpose.tls.auto.commonNameingressexpose.tls.secret.secretNametls.crt- the certificate;tls.key- the private keyexpose.ingress.hosts.corecore.harbor.domainexpose.ingress.controllerdefault,gce,alb,f5-bigipandncpdefaultexpose.ingress.kubeVersionOverrideexpose.ingress.classNameingressClassNameused to implement the Ingress (Kubernetes 1.18+)expose.ingress.annotationsexpose.ingress.labelsexpose.clusterIP.nameharborexpose.clusterIP.annotationsexpose.clusterIP.ports.httpPort80expose.clusterIP.ports.httpsPort443expose.clusterIP.annotationsexpose.clusterIP.labelsexpose.nodePort.nameharborexpose.nodePort.ports.http.port80expose.nodePort.ports.http.nodePort30002expose.nodePort.ports.https.port443expose.nodePort.ports.https.nodePort30003expose.nodePort.annotationsexpose.nodePort.labelsexpose.loadBalancer.nameharborexpose.loadBalancer.IP""expose.loadBalancer.ports.httpPort80expose.loadBalancer.ports.httpsPort30002expose.loadBalancer.annotationsexpose.loadBalancer.labelsexpose.loadBalancer.sourceRangesinternalTLS.enabledfalseinternalTLS.strong_ssl_ciphersfalseinternalTLS.certSourceauto,manual,secret.autointernalTLS.trustCacertSourceismanual. Note: all the internal certificates of the components must be issued by this CAinternalTLS.core.secretNamecertSourceissecret. The secret must contain keys named:ca.crt- the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA,tls.crt- the content of the TLS cert file,tls.key- the content of the TLS key file.internalTLS.core.crtcertSourceismanualinternalTLS.core.keycertSourceismanualinternalTLS.jobservice.secretNamecertSourceissecret. The secret must contain keys named:ca.crt- the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA,tls.crt- the content of the TLS cert file,tls.key- the content of the TLS key file.internalTLS.jobservice.crtcertSourceismanualinternalTLS.jobservice.keycertSourceismanualinternalTLS.registry.secretNamecertSourceissecret. The secret must contain keys named:ca.crt- the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA,tls.crt- the content of the TLS cert file,tls.key- the content of the TLS key file.internalTLS.registry.crtcertSourceismanualinternalTLS.registry.keycertSourceismanualinternalTLS.portal.secretNamecertSourceissecret. The secret must contain keys named:ca.crt- the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA,tls.crt- the content of the TLS cert file,tls.key- the content of the TLS key file.internalTLS.portal.crtcertSourceismanualinternalTLS.portal.keycertSourceismanualinternalTLS.trivy.secretNamecertSourceissecret. The secret must contain keys named:ca.crt- the CA certificate which is used to issue internal key and crt pair for components and all Harbor components must be issued by the same CA,tls.crt- the content of the TLS cert file,tls.key- the content of the TLS key file.internalTLS.trivy.crtcertSourceismanualinternalTLS.trivy.keycertSourceismanualipFamily.ipv4.enabledtrueipFamily.ipv6.enabledtruepersistence.enabledtruepersistence.resourcePolicykeepto avoid removing PVCs during a helm delete operation. Leaving it empty will delete PVCs after the chart deleted. Does not affect PVCs created for internal database and redis components.keeppersistence.persistentVolumeClaim.registry.existingClaimsubPathif the PVC is shared with other componentspersistence.persistentVolumeClaim.registry.storageClassstorageClassused to provision the volume. Or the default StorageClass will be used (the default). Set it to-to disable dynamic provisioningpersistence.persistentVolumeClaim.registry.subPathpersistence.persistentVolumeClaim.registry.accessModeReadWriteOncepersistence.persistentVolumeClaim.registry.size5Gipersistence.persistentVolumeClaim.registry.annotationspersistence.persistentVolumeClaim.jobservice.jobLog.existingClaimsubPathif the PVC is shared with other components.persistence.persistentVolumeClaim.jobservice.jobLog.storageClassstorageClassused to provision the volume. Or the default StorageClass will be used (the default). Set it to-to disable dynamic provisioningpersistence.persistentVolumeClaim.jobservice.jobLog.subPathpersistence.persistentVolumeClaim.jobservice.jobLog.accessModeReadWriteOncepersistence.persistentVolumeClaim.jobservice.jobLog.size1Gipersistence.persistentVolumeClaim.jobservice.jobLog.annotationspersistence.persistentVolumeClaim.database.existingClaimsubPathif the PVC is shared with other components. If external database is used, the setting will be ignoredpersistence.persistentVolumeClaim.database.storageClassstorageClassused to provision the volume. Or the default StorageClass will be used (the default). Set it to-to disable dynamic provisioning. If external database is used, the setting will be ignoredpersistence.persistentVolumeClaim.database.subPathpersistence.persistentVolumeClaim.database.accessModeReadWriteOncepersistence.persistentVolumeClaim.database.size1Gipersistence.persistentVolumeClaim.database.annotationspersistence.persistentVolumeClaim.redis.existingClaimsubPathif the PVC is shared with other components. If external Redis is used, the setting will be ignoredpersistence.persistentVolumeClaim.redis.storageClassstorageClassused to provision the volume. Or the default StorageClass will be used (the default). Set it to-to disable dynamic provisioning. If external Redis is used, the setting will be ignoredpersistence.persistentVolumeClaim.redis.subPathpersistence.persistentVolumeClaim.redis.accessModeReadWriteOncepersistence.persistentVolumeClaim.redis.size1Gipersistence.persistentVolumeClaim.redis.annotationspersistence.persistentVolumeClaim.trivy.existingClaimsubPathif the PVC is shared with other componentspersistence.persistentVolumeClaim.trivy.storageClassstorageClassused to provision the volume. Or the default StorageClass will be used (the default). Set it to-to disable dynamic provisioningpersistence.persistentVolumeClaim.trivy.subPathpersistence.persistentVolumeClaim.trivy.accessModeReadWriteOncepersistence.persistentVolumeClaim.trivy.size1Gipersistence.persistentVolumeClaim.trivy.annotationspersistence.imageChartStorage.disableredirects3storage type), please set it totrueto disable redirects. Refer to the guide for more detailsfalsepersistence.imageChartStorage.caBundleSecretNamecaBundleSecretNameif the storage service uses a self-signed certificate. The secret must contain keys namedca.crtwhich will be injected into the trust store of registry’s and containers.persistence.imageChartStorage.typefilesystem,azure,gcs,s3,swiftoross. The type must befilesystemif you want to use persistent volumes for registry. Refer to the guide for more detailsfilesystempersistence.imageChartStorage.gcs.existingSecret""persistence.imageChartStorage.gcs.useWorkloadIdentityserviceAccountNameof each component, then allow automounting the service account.falseexternalURLhttps://core.harbor.domaincaBundleSecretNameuaaSecretNameca.crt.imagePullPolicyimagePullSecretsupdateStrategy.typeRollingUpdateorRecreate. Set it asRecreatewhenRWMfor volumes isn’t supportedRollingUpdatelogLeveldebug,info,warning,errororfatalinfoharborAdminPasswordHarbor12345existingSecretAdminPasswordexistingSecretAdminPasswordKeyHARBOR_ADMIN_PASSWORDcaSecretNameca.crt. Setting this enables the download link on portal to download the CA certificate when the certificate isn’t generated automaticallysecretKeynot-a-secure-keyexistingSecretSecretKey""proxy.httpProxyproxy.httpsProxyproxy.noProxyproxy.componentsenableMigrateHelmHookfalseingress, Nginx will not be used)nginx.image.repositorygoharbor/nginx-photonnginx.image.tagdevnginx.replicas1nginx.revisionHistoryLimit10nginx.resourcesnginx.automountServiceAccountTokenfalsenginx.nodeSelector{}nginx.tolerations[]nginx.affinity{}nginx.topologySpreadConstraints[]nginx.podAnnotations{}nginx.priorityClassNameportal.image.repositorygoharbor/harbor-portalportal.image.tagdevportal.replicas1portal.revisionHistoryLimit10portal.resourcesportal.automountServiceAccountTokenfalseportal.nodeSelector{}portal.tolerations[]portal.affinity{}portal.topologySpreadConstraints[]portal.podAnnotations{}portal.serviceAnnotations{}portal.priorityClassNameportal.initContainers[]core.image.repositorygoharbor/harbor-corecore.image.tagdevcore.replicas1core.revisionHistoryLimit10core.startupProbe.initialDelaySeconds10core.resourcescore.automountServiceAccountTokenfalsecore.nodeSelector{}core.tolerations[]core.affinity{}core.topologySpreadConstraints[]core.podAnnotations{}core.serviceAnnotations{}core.configureUserSettingsCONFIG_OVERWRITE_JSONto configure user settings. See the [official docs](https://goharbor.io/docs/latest/install-config/configure-system-settings-cli/#set-configuration-items-using-an-environment-variable.core.quotaUpdateProviderredisordb. You can set it to be implemented byrediswhich can improve the performance of high concurrent pushing to the same project, and reduce database connection spikes and occupies. Using redis will bring up some delay for quota usage update for display, so only suggest switch provider to redis if you ran into the db connections spike around the scenario of high concurrent pushing to same project, no improvement for other scenes.dbcore.secretcore.secretNametls.crt- the certificate andtls.key- the private key. The default key pair will be used if it isn’t setcore.tokenKeycore.secretNameis unset. If set,core.tokenCertMUST also be set.core.tokenCertcore.tokenKeyused to validate service tokens. Only used ifcore.secretNameis unset. If set,core.tokenKeyMUST also be set.core.xsrfKeycore.priorityClassNamecore.artifactPullAsyncFlushDurationcore.gdpr.deleteUserfalsecore.gdpr.auditLogsCompliantfalsecore.initContainers[]jobservice.image.repositorygoharbor/harbor-jobservicejobservice.image.tagdevjobservice.replicas1jobservice.revisionHistoryLimit10jobservice.maxJobWorkers10jobservice.jobLoggersfile,databaseorstdout[file]jobservice.loggerSweeperDurationjobLoggersis set tostdout)14jobservice.notification.webhook_job_max_retry3jobservice.notification.webhook_job_http_client_timeout3jobservice.registryHttpClientTimeout30jobservice.reaper.max_update_hours24jobservice.reaper.max_dangling_hours168jobservice.resourcesjobservice.automountServiceAccountTokenfalsejobservice.nodeSelector{}jobservice.tolerations[]jobservice.affinity{}jobservice.topologySpreadConstraints[]jobservice.podAnnotations{}jobservice.priorityClassNamejobservice.secretjobservice.initContainers[]registry.registry.image.repositorygoharbor/registry-photonregistry.registry.image.tagdevregistry.registry.resourcesregistry.controller.image.repositorygoharbor/harbor-registryctlregistry.controller.image.tagdevregistry.controller.resourcesregistry.replicas1registry.revisionHistoryLimit10registry.nodeSelector{}registry.automountServiceAccountTokenfalseregistry.tolerations[]registry.affinity{}registry.topologySpreadConstraints[]registry.middlewaredocker pullrecipient. See official docs.registry.podAnnotations{}registry.priorityClassNameregistry.secretregistry.credentials.usernameregistry.credentials.password, a htpasswd is created. This is an alternative to providingregistry.credentials.htpasswdString. For more details see official docs.harbor_registry_userregistry.credentials.passwordregistry.credentials.username, a htpasswd is created. This is an alternative to providingregistry.credentials.htpasswdString. For more details see official docs. It is suggested you update this value before installation.harbor_registry_passwordregistry.credentials.existingSecretREGISTRY_PASSWD""registry.credentials.htpasswdStringregistry.credentials.usernameandregistry.credentials.password. May come in handy when integrating with tools like argocd or flux. This allows the same line to be generated each time the template is rendered, instead of thehtpasswdfunction from helm, which generates different lines each time because of the salt.registry.relativeurlsfalseregistry.upload_purging.enabledtrueregistry.upload_purging.age168hregistry.upload_purging.interval24hregistry.upload_purging.dryrunfalseregistry.initContainers[]trivy.enabledtruetrivy.image.repositorygoharbor/trivy-adapter-photontrivy.image.tagdevtrivy.resourcestrivy.automountServiceAccountTokenfalsetrivy.replicas1trivy.debugModefalsetrivy.vulnTypeosandlibrary.os,librarytrivy.severityUNKNOWN,LOW,MEDIUM,HIGH,CRITICALtrivy.ignoreUnfixedfalsetrivy.insecurefalsetrivy.skipUpdatefalsetrivy.skipJavaDBUpdatetrivy-java.dbfile Trivy Java DB and mount it in the/home/scanner/.cache/trivy/java-db/trivy-java.dbpathfalsetrivy.dbRepositorymirror.gcr.io/aquasec/trivy-db,ghcr.io/aquasecurity/trivy-dbtrivy.javaDBRepositorymirror.gcr.io/aquasec/trivy-java-db,ghcr.io/aquasecurity/trivy-java-dbtrivy.offlineScanfalsetrivy.securityCheckvulntrivy.timeout5m0strivy.gitHubTokentrivy.priorityClassNametrivy.topologySpreadConstraintstrivy.initContainers[]database.typeexternalinternaldatabase.internal.image.repositorygoharbor/harbor-dbdatabase.internal.image.tagdevdatabase.internal.passwordchangeitdatabase.internal.shmSizeLimit512Midatabase.internal.resourcesdatabase.internal.automountServiceAccountTokenfalsedatabase.internal.initContainer.migrator.resourcesdatabase.internal.initContainer.permissions.resourcesdatabase.internal.nodeSelector{}database.internal.tolerations[]database.internal.affinity{}database.internal.priorityClassNamedatabase.internal.livenessProbe.timeoutSecondsdatabase.internal.readinessProbe.timeoutSecondsdatabase.internal.extrInitContainers[]database.external.host192.168.0.1database.external.port5432database.external.usernameuserdatabase.external.passwordpassworddatabase.external.coreDatabaseregistrydatabase.external.existingSecretpassword.""database.external.sslmodedisabledatabase.maxIdleConns50database.maxOpenConns100database.podAnnotations{}redis.typeexternalinternalredis.internal.image.repositorygoharbor/valkey-photonredis.internal.image.tagdevredis.internal.resourcesredis.internal.automountServiceAccountTokenfalseredis.internal.nodeSelector{}redis.internal.tolerations[]redis.internal.affinity{}redis.internal.priorityClassNameredis.internal.jobserviceDatabaseIndex1redis.internal.registryDatabaseIndex2redis.internal.trivyAdapterIndex5redis.internal.harborDatabaseIndex0redis.internal.cacheLayerDatabaseIndex0redis.internal.initContainers[]redis.external.addr192.168.0.2:6379redis.external.sentinelMasterSetredis.external.coreDatabaseIndex0redis.external.jobserviceDatabaseIndex1redis.external.registryDatabaseIndex2redis.external.trivyAdapterIndex5redis.external.harborDatabaseIndex0redis.external.cacheLayerDatabaseIndex0redis.external.usernameredis.external.passwordredis.external.existingSecretREDIS_PASSWORD.""redis.podAnnotations{}exporter.replicas1exporter.revisionHistoryLimit10exporter.podAnnotations{}exporter.image.repositorygoharbor/harbor-exporterexporter.image.tagdevexporter.nodeSelector{}exporter.tolerations[]exporter.affinity{}exporter.topologySpreadConstraints[]exporter.automountServiceAccountTokenfalseexporter.cacheDuration30exporter.cacheCleanInterval14400exporter.priorityClassNamemetrics.enabledfalsemetrics.core.path/metricsmetrics.core.port8001metrics.registry.path/metricsmetrics.registry.port8001metrics.exporter.path/metricsmetrics.exporter.port8001metrics.serviceMonitor.enabledfalsemetrics.serviceMonitor.additionalLabels""metrics.serviceMonitor.interval""metrics.serviceMonitor.metricRelabelings[]metrics.serviceMonitor.relabelings[]trace.enabledfalsetrace.providerjaegerorotel.jaegershould be 1.26+jaegertrace.sample_ratesample_rateto 1 if you want sampling 100% of trace data; set 0.5 if you want sampling 50% of trace data, and so forth1trace.namespacetrace.attributesattributesis a key value dict contains user defined attributes used to initialize trace providertrace.jaeger.endpointhttp://hostname:14268/api/tracestrace.jaeger.usernametrace.jaeger.passwordtrace.jaeger.agent_hosttrace.jaeger.agent_port6831trace.otel.endpointhostname:4318trace.otel.url_path/v1/tracestrace.otel.compressionfalsetrace.otel.insecuretruetrace.otel.timeout10cache.enabledfalsecache.expireHours24Harbor Kubernetes Version Compatibility Matrix
The following is a list of the Test Kubernetes versions for each Harbor version. Generally, Harbor supporting Kubernetes version above v1.20+ . However we only test against 3 Kubernetes minor versions for each Harbor minor release.