Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-07-05 19:26:23 +02:00
Code Issues Projects Releases Wiki Activity

update installation guide

Browse Source
This commit is contained in:
Henry Zhang 2016-11-23 23:35:57 +08:00
parent ee7ad59143
commit 0c62b50606
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/installation_guide_ova.md
View File

@ -20,7 +20,7 @@ By default, Harbor uses HTTPS for secure communication. A self-signed certificat
Harbor always tries to generate a self-signed certificate based on its FQDN. Therefore, its IP address must have a FQDN associated with it in the DNS server. If Harbor cannot resolve its IP address to a FQDN, it generates the self-signed certificate using its IP address. In this case, Harbor can only be accessed by IP address.
If Harbor's IP address or FQDN is changed, the self-signed certificate will be re-generated. However, since the certificate of Harbor's own CA does not change, no certificate update is needed in the Docker client or VCH.
When Harbor's IP address or FQDN is changed, the self-signed certificate will be re-generated. However, since the certificate of Harbor's own CA does not change, no certificate update is needed in the Docker client or VCH.
Harbor's self-generated certificate can be replaced by supplying a certificate signed by other CAs in OVA's settings.