Upstream
/
harbor
mirror of https://github.com/goharbor/harbor.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
4,861 Commits 46 Branches 299 Tags 356 MiB
Commit Graph

6 Commits

Author SHA1 Message Date
Wenkai Yin c72a7db4be Fix misc issues of Harbor charts 
1. Fix the pull/push commands showed on UI are incorrect
2. Replace "insecureRegistry" with "externalProtocol"
3. Using the secret rather than pasting text if users want to use the certificate of themselves
4. Refine NOTES.txt
 2018-07-11 17:16:42 +08:00
Wenkai Yin 6bb2bbb3ce Modify chart to support master branch 
The chart currently is using images of Harbor 1.5 which contains three databases, this commit reduce them to only one to support master branch codes.
 2018-07-05 14:27:48 +08:00
Daniel Jiang 8cd90b6809 Add externalPort in values.yaml 
Fixes #5133
Provide more flexibility for ingress controller setting.  When the
ingress controller is not exposing 80/443 port, user can set `externalPort` to expose the endpoint of Harbor.
 2018-06-16 12:17:29 +08:00
Tan Jiang 065fbfa1a1 Make Helm Chart support Harbor 1.5.0 
Update the helm chart of Harbor to use 1.5 image.  Specifically
`1.5.0-chart-patch` to include the fix to #4496 (for integration reason
this fix will not be merge to release branch).
Verified against kubenetes v1.10.0
 2018-05-21 00:06:17 +08:00
Jesse Hu d0cf95333c [Chart] Fix a ConfigMap mount issue in K8s 1.10 
K8s 1.10 throws error when mounting a file into the directory which
is also mounted from a ConfigMap.
Fix issue https://github.com/vmware/harbor/issues/4886
 2018-05-10 18:37:46 +08:00
Jesse Hu ce48dbfec2 [Chart] Add support for deploying Notary 
Assuming Harbor FQDN is specified as harbor.my.domain by the user,
the Notary server FQDN will be set to notary-harbor.my.domain.
So the user must point both Harbor FQDN and Notary FQDN to the K8s
ingress controller IP in the DNS server.

Fix issue https://github.com/vmware/harbor/issues/4394
 2018-04-19 15:17:33 +08:00