2019-05-16 09:15:42 +02:00
# Configuration file of Harbor
2016-04-04 08:04:02 +02:00
2019-05-16 09:15:42 +02:00
# The IP address or hostname to access admin UI and registry service.
# DO NOT use localhost or 127.0.0.1, because Harbor needs to be accessed by external clients.
2018-11-15 04:09:57 +01:00
hostname: reg.mydomain.com
2019-04-09 11:19:05 +02:00
2019-04-29 12:51:00 +02:00
# http related config
2019-04-01 08:20:16 +02:00
http:
2019-04-09 11:19:05 +02:00
# port for http, default is 80. If https enabled, this port will redirect to https port
2019-04-01 08:20:16 +02:00
port: 80
2019-04-02 09:21:50 +02:00
2019-04-29 12:51:00 +02:00
# https related config
2019-10-23 08:08:15 +02:00
https:
# https port for harbor, default is 443
port: 443
# The path of cert and key files for nginx
certificate: /your/certificate/path
private_key: /your/private/key/path
2019-04-01 08:20:16 +02:00
2020-03-16 17:52:54 +01:00
# # Uncomment following will enable tls communication between all harbor components
2020-03-16 16:20:05 +01:00
# internal_tls:
2020-03-19 20:04:10 +01:00
# # set enabled to true means internal tls is enabled
2020-03-16 16:20:05 +01:00
# enabled: true
2020-03-19 20:04:10 +01:00
# # put your cert and key files on dir
2020-03-16 16:20:05 +01:00
# dir: /etc/harbor/tls/internal
2020-02-11 06:47:55 +01:00
2019-04-29 12:51:00 +02:00
# Uncomment external_url if you want to enable external proxy
# And when it enabled the hostname will no longer used
2019-04-01 08:20:16 +02:00
# external_url: https://reg.mydomain.com:8433
# The initial password of Harbor admin
# It only works in first time to install harbor
# Remember Change the admin password from UI after launching Harbor.
2018-11-15 04:09:57 +01:00
harbor_admin_password: Harbor12345
2016-04-04 08:04:02 +02:00
2019-05-16 09:15:42 +02:00
# Harbor DB configuration
2019-02-25 11:16:35 +01:00
database:
2019-05-16 09:15:42 +02:00
# The password for the root user of Harbor DB. Change this before any production use.
2019-02-25 11:16:35 +01:00
password: root123
2019-08-12 11:14:57 +02:00
# The maximum number of connections in the idle connection pool. If it <=0, no idle connections are retained.
2021-06-15 12:39:15 +02:00
max_idle_conns: 100
2019-08-12 11:14:57 +02:00
# The maximum number of open connections to the database. If it <= 0, then there is no limit on the number of open connections.
2020-07-14 09:33:01 +02:00
# Note: the default number of connections is 1024 for postgres of harbor.
2021-06-15 12:39:15 +02:00
max_open_conns: 900
2022-11-30 12:08:08 +01:00
# The maximum amount of time a connection may be reused. Expired connections may be closed lazily before reuse. If it <= 0, connections are not closed due to a connection's age.
# The value is a duration string. A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
conn_max_lifetime: 5m
# The maximum amount of time a connection may be idle. Expired connections may be closed lazily before reuse. If it <= 0, connections are not closed due to a connection's idle time.
# The value is a duration string. A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
conn_max_idle_time: 0
2019-02-25 11:16:35 +01:00
2019-04-01 08:20:16 +02:00
# The default data volume
data_volume: /data
2019-02-25 11:16:35 +01:00
2019-04-02 14:08:26 +02:00
# Harbor Storage settings by default is using /data dir on local filesystem
# Uncomment storage_service setting If you want to using external storage
# storage_service:
# # ca_bundle is the path to the custom root ca certificate, which will be injected into the truststore
2023-02-16 11:11:05 +01:00
# # of registry's containers. This is usually needed when the user hosts a internal storage with self signed certificate.
2019-04-02 14:08:26 +02:00
# ca_bundle:
2019-04-01 08:20:16 +02:00
2019-04-02 14:08:26 +02:00
# # storage backend, default is filesystem, options include filesystem, azure, gcs, s3, swift and oss
# # for more info about this configuration please refer https://docs.docker.com/registry/configuration/
# filesystem:
# maxthreads: 100
2019-04-30 11:05:27 +02:00
# # set disable to true when you want to disable registry redirect
# redirect:
2023-03-22 06:55:22 +01:00
# disable: false
2019-02-25 11:16:35 +01:00
2020-03-12 09:37:41 +01:00
# Trivy configuration
2020-08-10 08:48:04 +02:00
#
# Trivy DB contains vulnerability information from NVD, Red Hat, and many other upstream vulnerability databases.
# It is downloaded by Trivy from the GitHub release page https://github.com/aquasecurity/trivy-db/releases and cached
# in the local file system. In addition, the database contains the update timestamp so Trivy can detect whether it
# should download a newer version from the Internet or use the cached one. Currently, the database is updated every
# 12 hours and published as a new release to GitHub.
2020-03-12 09:37:41 +01:00
trivy:
2020-03-18 17:11:43 +01:00
# ignoreUnfixed The flag to display only fixed vulnerabilities
ignore_unfixed: false
# skipUpdate The flag to enable or disable Trivy DB downloads from GitHub
#
# You might want to enable this flag in test or CI/CD environments to avoid GitHub rate limiting issues.
2020-08-10 08:48:04 +02:00
# If the flag is enabled you have to download the `trivy-offline.tar.gz` archive manually, extract `trivy.db` and
# `metadata.json` files and mount them in the `/home/scanner/.cache/trivy/db` path.
2020-03-18 17:11:43 +01:00
skip_update: false
2020-04-15 20:08:00 +02:00
#
2022-01-19 10:42:12 +01:00
# The offline_scan option prevents Trivy from sending API requests to identify dependencies.
# Scanning JAR files and pom.xml may require Internet access for better detection, but this option tries to avoid it.
# For example, the offline mode will not try to resolve transitive dependencies in pom.xml when the dependency doesn't
# exist in the local repositories. It means a number of detected vulnerabilities might be fewer in offline mode.
# It would work if all the dependencies are in local.
2022-12-21 02:56:12 +01:00
# This option doesn't affect DB download. You need to specify "skip-update" as well as "offline-scan" in an air-gapped environment.
2022-01-19 10:42:12 +01:00
offline_scan: false
#
2022-10-25 08:26:53 +02:00
# Comma-separated list of what security issues to detect. Possible values are `vuln`, `config` and `secret`. Defaults to `vuln`.
security_check: vuln
#
2020-04-15 20:08:00 +02:00
# insecure The flag to skip verifying registry certificate
insecure: false
2020-03-12 09:37:41 +01:00
# github_token The GitHub access token to download Trivy DB
#
# Anonymous downloads from GitHub are subject to the limit of 60 requests per hour. Normally such rate limit is enough
# for production operations. If, for any reason, it's not enough, you could increase the rate limit to 5000
# requests per hour by specifying the GitHub access token. For more details on GitHub rate limiting please consult
# https://developer.github.com/v3/ #rate - limiting
#
2020-08-10 08:48:04 +02:00
# You can create a GitHub token by following the instructions in
2020-03-12 09:37:41 +01:00
# https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
#
# github_token: xxx
2019-04-01 08:20:16 +02:00
jobservice:
2019-08-12 11:14:57 +02:00
# Maximum number of job workers in job service
2019-04-01 08:20:16 +02:00
max_job_workers: 10
2023-03-18 03:46:40 +01:00
# The jobLogger sweeper duration (ignored if `jobLogger` is `stdout`)
logger_sweeper_duration: 1 #days
2019-04-01 08:20:16 +02:00
2019-08-07 14:56:31 +02:00
notification:
# Maximum retry count for webhook job
2023-03-22 10:36:50 +01:00
webhook_job_max_retry: 3
2023-03-21 04:54:10 +01:00
# HTTP client timeout for webhook job
webhook_job_http_client_timeout: 3 #seconds
2019-08-07 14:56:31 +02:00
2019-04-01 08:20:16 +02:00
# Log configurations
log:
2019-05-15 04:28:52 +02:00
# options are debug, info, warning, error, fatal
2019-04-01 08:20:16 +02:00
level: info
2019-06-21 08:18:28 +02:00
# configs for logs in local storage
local:
# Log files are rotated log_rotate_count times before being removed. If count is 0, old versions are removed rather than rotated.
rotate_count: 50
2019-08-12 11:14:57 +02:00
# Log files are rotated only if they grow bigger than log_rotate_size bytes. If size is followed by k, the size is assumed to be in kilobytes.
# If the M is used, the size is in megabytes, and if G is used, the size is in gigabytes. So size 100, size 100k, size 100M and size 100G
2019-06-21 08:18:28 +02:00
# are all valid.
rotate_size: 200M
# The directory on your host that store log
location: /var/log/harbor
# Uncomment following lines to enable external syslog endpoint.
# external_endpoint:
# # protocol used to transmit log to external endpoint, options is tcp or udp
# protocol: tcp
# # The host of external endpoint
# host: localhost
# # Port of external endpoint
# port: 5140
2019-04-01 08:20:16 +02:00
#This attribute is for migrator to detect the version of the . cfg file , DO NOT MODIFY !
2023-03-18 03:46:40 +01:00
_version: 2.8.0
2018-03-15 07:21:53 +01:00
2019-05-14 05:26:44 +02:00
# Uncomment external_database if using external database.
2019-04-01 08:20:16 +02:00
# external_database:
2019-05-10 04:44:05 +02:00
# harbor:
2019-05-10 07:41:47 +02:00
# host: harbor_db_host
# port: harbor_db_port
# db_name: harbor_db_name
# username: harbor_db_username
# password: harbor_db_password
2019-05-10 04:44:05 +02:00
# ssl_mode: disable
2019-08-29 09:04:10 +02:00
# max_idle_conns: 2
# max_open_conns: 0
2019-05-10 04:44:05 +02:00
# notary_signer:
2019-05-10 07:41:47 +02:00
# host: notary_signer_db_host
# port: notary_signer_db_port
# db_name: notary_signer_db_name
# username: notary_signer_db_username
# password: notary_signer_db_password
2019-05-10 04:44:05 +02:00
# ssl_mode: disable
# notary_server:
2019-05-10 07:41:47 +02:00
# host: notary_server_db_host
# port: notary_server_db_port
# db_name: notary_server_db_name
# username: notary_server_db_username
# password: notary_server_db_password
2019-05-10 04:44:05 +02:00
# ssl_mode: disable
2019-04-01 08:20:16 +02:00
2019-04-29 12:51:00 +02:00
# Uncomment external_redis if using external Redis server
2019-04-01 08:20:16 +02:00
# external_redis:
2020-06-15 18:20:18 +02:00
# # support redis, redis+sentinel
# # host for redis: <host_redis>:<port_redis>
# # host for redis+sentinel:
# # <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
# host: redis:6379
2022-02-11 10:28:10 +01:00
# password:
2023-03-17 07:16:19 +01:00
# # Redis AUTH command was extended in Redis 6, it is possible to use it in the two-arguments AUTH <username> <password> form.
# # username:
2020-06-15 18:20:18 +02:00
# # sentinel_master_set must be set to support redis+sentinel
# #sentinel _master_set :
2019-04-01 08:20:16 +02:00
# # db_index 0 is for core, it's unchangeable
# registry_db_index: 1
# jobservice_db_index: 2
2020-02-13 17:57:02 +01:00
# trivy_db_index: 5
2020-02-23 05:31:56 +01:00
# idle_timeout_seconds: 30
2019-05-06 10:32:00 +02:00
# Uncomment uaa for trusting the certificate of uaa instance that is hosted via self-signed cert.
# uaa:
2019-05-10 04:44:05 +02:00
# ca_file: /path/to/ca
2019-08-10 17:59:33 +02:00
# Global proxy
# Config http proxy for components, e.g. http://my.proxy.com:3128
# Components doesn't need to connect to each others via http proxy.
# Remove component from `components` array if want disable proxy
# for it. If you want use proxy for replication, MUST enable proxy
# for core and jobservice, and set `http_proxy` and `https_proxy`.
# Add domain to the `no_proxy` field, when you want disable proxy
# for some special registry.
proxy:
http_proxy:
https_proxy:
2019-11-25 10:28:11 +01:00
no_proxy:
2019-08-10 17:59:33 +02:00
components:
- core
- jobservice
2020-03-14 22:41:43 +01:00
- trivy
2020-10-18 18:16:02 +02:00
# metric:
# enabled: false
# port: 9090
# path: /metrics
2021-08-23 09:08:49 +02:00
2021-08-27 18:24:14 +02:00
# Trace related config
# only can enable one trace provider(jaeger or otel) at the same time,
# and when using jaeger as provider, can only enable it with agent mode or collector mode.
# if using jaeger collector mode, uncomment endpoint and uncomment username, password if needed
# if using jaeger agetn mode uncomment agent_host and agent_port
# trace:
# enabled: true
# # set sample_rate to 1 if you wanna sampling 100% of trace data; set 0.5 if you wanna sampling 50% of trace data, and so forth
# sample_rate: 1
2021-09-17 18:07:24 +02:00
# # # namespace used to differenciate different harbor services
2021-08-27 18:24:14 +02:00
# # namespace:
# # # attributes is a key value dict contains user defined attributes used to initialize trace provider
# # attributes:
# # application: harbor
2021-10-22 07:43:28 +02:00
# # # jaeger should be 1.26 or newer.
2021-08-27 18:24:14 +02:00
# # jaeger:
# # endpoint: http://hostname:14268/api/traces
# # username:
# # password:
# # agent_host: hostname
2021-10-22 07:43:28 +02:00
# # # export trace data by jaeger.thrift in compact mode
# # agent_port: 6831
2021-08-27 18:24:14 +02:00
# # otel:
# # endpoint: hostname:4318
# # url_path: /v1/traces
# # compression: false
# # insecure: true
2023-08-15 04:09:41 +02:00
# # # timeout is in seconds
# # timeout: 10
2021-12-16 09:00:07 +01:00
2022-12-21 02:56:12 +01:00
# Enable purge _upload directories
2021-12-16 09:00:07 +01:00
upload_purging:
enabled: true
# remove files in _upload directories which exist for a period of time, default is one week.
age: 168h
# the interval of the purge operations
interval: 24h
dryrun: false
2022-03-25 10:59:37 +01:00
2022-12-21 02:56:12 +01:00
# Cache layer configurations
2022-08-04 09:14:45 +02:00
# If this feature enabled, harbor will cache the resource
# `project/project_metadata/repository/artifact/manifest` in the redis
# which can especially help to improve the performance of high concurrent
# manifest pulling.
# NOTICE
# If you are deploying Harbor in HA mode, make sure that all the harbor
# instances have the same behaviour, all with caching enabled or disabled,
# otherwise it can lead to potential data inconsistency.
2022-03-25 10:59:37 +01:00
cache:
2022-08-04 09:14:45 +02:00
# not enabled by default
2022-03-25 10:59:37 +01:00
enabled: false
2022-08-04 09:14:45 +02:00
# keep cache for one day by default
2022-03-25 10:59:37 +01:00
expire_hours: 24