暂无图片
暂无图片
暂无图片
暂无图片
暂无图片
首页 / Helm部署Harbor

Helm部署Harbor

ItTalk 2019-10-08
2141

Harbor简介

Harbor是一个开源的云原生仓库，提供类似https://hub.docker.com的功能，它扩展了开源Docker Distribution，适合公司内部做为容器镜像管理。详细可参考：https://github.com/goharbor/harbor

为何选择部署私服仓库？

选择自己部署私服的原因主要有二，其一为生产环境的镜像很大（200-300M），为了提高CI/CD的速度，部署私库可提升效率。其二为保护自制镜像的安全。

Helm部署harbor

我们选择bitnami的Charts，它是基于官方的harbor-helm(https://github.com/goharbor/harbor-helm) ，并做了一些增强，这里不做赘述。
  1. #添加helm仓库
  2. helm repo add bitnami https://charts.bitnami.com
  3. #fetch charts，并解压
  4. helm fetch --untar bitnami/harbor
  5. #修改配置文件values-production.yaml
  6. 1）修改全局storgeClass，我这里使用的是nfs，具体的sc为nfs-client，具体配置时请根据实际情况做调整
  7. global:
  8.   storageClass: nfs-client
  9. 2）修改service的类型，请根据实际情况调整
  10. service:
  11.   type: NodePort
  12. 3）关闭tls功能，具体请根据情况做调整
  13. service:
  14.   tls:
  15.     enabled: false
  16. 4）定义NodePort端口
  17. service:
  18.   nodePort:
  19.     ports:
  20.       http:
  21.         nodePort: 31080
  22. 5）调整仓库卷的大小，请根据情况做调整
  23. persistence:
  24.   persistentVolumeClaim:
  25.     registry:
  26.       size: 200G
  27. 6）设置externalURL
  28. externalURL: xxx.example.org
  29. #安装部署
  30. helm install bitnami/harbor -f values-production.yaml  --name sre-harbor  --namespace sre

  32. #结果显示
  33. NAME:   sre-harbor
  34. LAST DEPLOYED: Thu Sep 19 17:34:27 2019
  35. NAMESPACE: sre
  36. STATUS: DEPLOYED

  38. RESOURCES:
  39. ==> v1/Secret
  40. NAME                           TYPE    DATA  AGE
  41. sre-harbor-postgresql          Opaque  1     1s
  42. sre-harbor-chartmuseum-secret  Opaque  1     1s
  43. sre-harbor-core-envvars        Opaque  3     1s
  44. sre-harbor-core                Opaque  4     1s
  45. sre-harbor-jobservice          Opaque  1     1s
  46. sre-harbor-registry            Opaque  2     1s

  48. ==> v1/ConfigMap
  49. NAME                                DATA  AGE
  50. sre-harbor-postgresql-init-scripts  3     1s
  51. sre-harbor-redis                    3     1s
  52. sre-harbor-redis-health             6     1s
  53. sre-harbor-chartmuseum-envvars      15    1s
  54. sre-harbor-clair                    1     1s
  55. sre-harbor-core-envvars             34    1s
  56. sre-harbor-core                     1     1s
  57. sre-harbor-jobservice               1     1s
  58. sre-harbor-nginx                    1     1s
  59. sre-harbor-notary-server            5     1s
  60. sre-harbor-registry                 2     1s

  62. ==> v1/PersistentVolumeClaim
  63. NAME                    STATUS  VOLUME                                    CAPACITY  ACCESS MODES  STORAGECLASS  AGE
  64. sre-harbor-chartmuseum  Bound   pvc-ada5239a-dac0-11e9-b579-00163e064a2f  5Gi       RWO           nfs-client    1s
  65. sre-harbor-jobservice   Bound   pvc-ada5bc62-dac0-11e9-b579-00163e064a2f  1Gi       RWO           nfs-client    1s
  66. sre-harbor-registry     Bound   pvc-ada67232-dac0-11e9-b579-00163e064a2f  200Gi     RWO           nfs-client    1s

  68. ==> v1/Service
  69. NAME                            TYPE       CLUSTER-IP       EXTERNAL-IP  PORT(S)                      AGE
  70. sre-harbor-postgresql-headless  ClusterIP  None             <none>       5432/TCP                     1s
  71. sre-harbor-postgresql           ClusterIP  192.168.230.120  <none>       5432/TCP                     1s
  72. sre-harbor-redis-headless       ClusterIP  None             <none>       6379/TCP                     1s
  73. sre-harbor-redis-master         ClusterIP  192.168.155.133  <none>       6379/TCP                     1s
  74. sre-harbor-chartmuseum          ClusterIP  192.168.254.236  <none>       80/TCP                       1s
  75. sre-harbor-clair                ClusterIP  192.168.108.2    <none>       6060/TCP,6061/TCP            1s
  76. sre-harbor-core                 ClusterIP  192.168.171.198  <none>       80/TCP                       1s
  77. sre-harbor-jobservice           ClusterIP  192.168.19.27    <none>       80/TCP                       1s
  78. sre-harbor                      NodePort   192.168.225.35   <none>       80:31080/TCP,4443:30004/TCP  1s
  79. sre-harbor-notary-server        ClusterIP  192.168.92.252   <none>       4443/TCP                     1s
  80. sre-harbor-notary-signer        ClusterIP  192.168.72.54    <none>       7899/TCP                     1s
  81. sre-harbor-portal               ClusterIP  192.168.90.132   <none>       80/TCP                       1s
  82. sre-harbor-registry             ClusterIP  192.168.43.96    <none>       5000/TCP,8080/TCP            1s

  84. ==> v1/Deployment
  85. NAME                      DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
  86. sre-harbor-chartmuseum    1        1        1           0          1s
  87. sre-harbor-clair          1        1        1           0          1s
  88. sre-harbor-core           1        1        1           0          1s
  89. sre-harbor-jobservice     1        1        1           0          1s
  90. sre-harbor-notary-server  1        0        0           0          1s
  91. sre-harbor-notary-signer  1        0        0           0          1s
  92. sre-harbor-portal         1        0        0           0          0s
  93. sre-harbor-registry       1        0        0           0          0s

  95. ==> v1beta1/Deployment
  96. NAME              DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
  97. sre-harbor-nginx  1        1        1           0          1s

  99. ==> v1beta2/StatefulSet
  100. NAME                     DESIRED  CURRENT  AGE
  101. sre-harbor-postgresql    1        1        0s
  102. sre-harbor-redis-master  1        1        0s

  104. ==> v1/Pod(related)
  105. NAME                                       READY  STATUS             RESTARTS  AGE
  106. sre-harbor-chartmuseum-5f9d96f89f-bndxc    0/1    ContainerCreating  0         1s
  107. sre-harbor-clair-79d997654c-bns26          0/1    ContainerCreating  0         1s
  108. sre-harbor-core-56ddbb48f7-qrvsv           0/1    ContainerCreating  0         1s
  109. sre-harbor-jobservice-5c8fbfbb-mrp5z       0/1    ContainerCreating  0         1s
  110. sre-harbor-nginx-8fd6fc5b7-m7kwf           0/1    ContainerCreating  0         1s
  111. sre-harbor-notary-server-86dc474cf6-p2nq2  0/1    ContainerCreating  0         0s
  112. sre-harbor-notary-signer-67ff9f56b6-fskdt  0/1    Pending            0         0s
  113. sre-harbor-portal-85ccdcd75-fdvx6          0/1    Pending            0         0s
  114. sre-harbor-registry-66f4b897ff-945dk       0/2    Pending            0         0s
  115. sre-harbor-postgresql-0                    0/1    Pending            0         0s
  116. sre-harbor-redis-master-0                  0/1    Pending            0         0s


  119. NOTES:
  120. ** Please be patient while the chart is being deployed **

  122. 1. Get the Harbor URL:

  124.   export NODE_PORT=$(kubectl get --namespace sre -o jsonpath="{.spec.ports[0].nodePort}" services sre-harbor)
  125.   export NODE_IP=$(kubectl get nodes --namespace sre -o jsonpath="{.items[0].status.addresses[0].address}")
  126.   echo "Harbor URL: http://$NODE_IP:$NODE_PORT/"

  128. 2. Login with the following credentials to see your Harbor application

  130.   echo Username: "admin"
  131.   echo Password: $(kubectl get secret --namespace sre sre-harbor-core-envvars -o jsonpath="{.data.HARBOR_ADMIN_PASSWORD}" | base64 --decode)

nginx配置

通过外部nginx反向代理到k8s NodePort即可，有两个地方要注意：

  • 解析到nginx的域名需要和externalURL一致

  • 反向代理设置时，proxysetheader Host $host不能配置


数据库
文章转载自ItTalk，如果涉嫌侵权，请发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。

评论