kubernetes實踐之二十七:Harbor
一:簡介
三:主要元件
1、安裝python-pip
yum -y install epel-release
yum -y install python-pip
2、安裝docker-compose
pip install docker-compose
待安裝完成後,執行查詢版本的命令,即可安裝docker-compose
docker-compose version
3.安裝Harbor
wget
tar -zxvf harbor-offline-installer-v1.4.0.tgz
配置檔案 harbor.cfg
配置檔案docker-compose.yml
安裝Harbor
./install.sh
可以使用docker-compose來管理Harbor的生命週期。 一些有用的命令列出如下:
docker-compose ps 檢視
docker-compose stop 停止
docker-compose start 啟動
docker-compose down 刪除,利用./install.sh可以重新安裝
五:驗證
1.碰到的問題
a. 錯誤提示
原因:python庫中urllib3 (1.21.1) or chardet (2.2.1) 的版本不相容
解決辦法:
pip uninstall urllib3
pip uninstall chardet
pip install requests
b.錯誤提示:“harbor failed to initialize the system: read /etc/adminserver/key: is a directory”
原因:harbor.cfg中的secretkey_path和docker-compose.yml中的設定不一致
2.ui 介面
Harbor是一個用於儲存和分發Docker映象的企業級Registry伺服器。
映象的儲存harbor使用的是官方的docker registry(v2命名是distribution)服務去完成。harbor在docker distribution的基礎上增加了一些安全、訪問控制、管理的功能以滿足企業對於映象倉庫的需求。harbor以docker-compose的規範形式組織各個元件,並透過docker-compose工具進行啟停。
docker的registry是用本地儲存或者s3都是可以的,harbor的功能是在此之上提供使用者許可權管理、映象複製等功能,提高使用的registry的效率。Harbor的映象複製功能是透過docker registry的API去複製,這種做法遮蔽了繁瑣的底層檔案操作、不僅可以利用現有docker registry功能不必重複造輪子,而且可以解決衝突和一致性的問題。
二:Harbor架構三:主要元件
- Proxy:對應啟動元件nginx。它是一個nginx反向代理,代理Notary client(映象認證)、Docker client(映象上傳下載等)和瀏覽器的訪問請求(Core Service)給後端的各服務;
-
UI(Core Service):對應啟動元件harbor-ui。底層資料儲存使用mysql資料庫,主要提供了四個子功能:
- UI:一個web管理頁面ui;
- API:Harbor暴露的API服務;
- Auth:使用者認證服務,decode後的token中的使用者資訊在這裡進行認證;auth後端可以接db、ldap、uaa三種認證實現;
- Token服務(上圖中未體現):負責根據使用者在每個project中的role來為每一個docker push/pull命令issuing一個token,如果從docker client傳送給registry的請求沒有帶token,registry會重定向請求到token服務建立token。
- Registry:對應啟動元件registry。負責儲存映象檔案,和處理映象的pull/push命令。Harbor對映象進行強制的訪問控制,Registry會將客戶端的每個pull、push請求轉發到token服務來獲取有效的token。
- Admin Service:對應啟動元件harbor-adminserver。是系統的配置管理中心附帶檢查儲存用量,ui和jobserver啟動時候需要載入adminserver的配置;
- Job Sevice:對應啟動元件harbor-jobservice。負責映象複製工作的,他和registry通訊,從一個registry pull映象然後push到另一個registry,並記錄job_log;
- Log Collector:對應啟動元件harbor-log。日誌彙總元件,透過docker的log-driver把日誌彙總到一起;
- Volnerability Scanning:對應啟動元件clair。負責映象掃描
- Notary:對應啟動元件notary。負責映象認證
- DB:對應啟動元件harbor-db,負責儲存project、 user、 role、replication、image_scan、access等的metadata資料。
1、安裝python-pip
yum -y install epel-release
yum -y install python-pip
2、安裝docker-compose
pip install docker-compose
待安裝完成後,執行查詢版本的命令,即可安裝docker-compose
docker-compose version
3.安裝Harbor
wget
tar -zxvf harbor-offline-installer-v1.4.0.tgz
配置檔案 harbor.cfg
點選(此處)摺疊或開啟
-
## Configuration file of Harbor
-
-
#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.
-
hostname = 120.79.156.135
-
-
#The protocol for accessing the UI and token/notification service, by default it is http.
-
#It can be set to https if ssl is enabled on nginx.
-
ui_url_protocol = http
-
-
#Maximum number of job workers in job service
-
max_job_workers = 3
-
-
#Determine whether or not to generate certificate for the registry's token.
-
#If the value is on, the prepare script creates new root cert and private key
-
#for generating token to access the registry. If the value is off the default key/cert will be used.
-
#This flag also controls the creation of the notary signer's cert.
-
customize_crt = on
-
-
#The path of cert and key files for nginx, they are applied only the protocol is set to https
-
ssl_cert = /mnt/harbor/cert/server.crt
-
ssl_cert_key = /mnt/harbor/cert/server.key
-
-
#The path of secretkey storage
-
secretkey_path = /mnt/harbor
-
-
#Admiral's url, comment this attribute, or set its value to NA when Harbor is standalone
-
admiral_url = NA
-
-
#Log files are rotated log_rotate_count times before being removed. If count is 0, old versions are removed rather than rotated.
-
log_rotate_count = 50
-
#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
-
#are all valid.
-
log_rotate_size = 200M
-
-
#NOTES: The properties between BEGIN INITIAL PROPERTIES and END INITIAL PROPERTIES
-
#only take effect in the first boot, the subsequent changes of these properties
-
#should be performed on web ui
-
-
#************************BEGIN INITIAL PROPERTIES************************
-
-
#Email account settings for sending out password resetting emails.
-
-
#Email server uses the given username and password to authenticate on TLS connections to host and act as identity.
-
#Identity left blank to act as username.
-
email_identity =
-
-
email_server = smtp.mydomain.com
-
email_server_port = 25
-
email_username = sample_admin@mydomain.com
-
email_password = abc
-
email_from = admin <sample_admin@mydomain.com>
-
email_ssl = false
-
email_insecure = false
-
-
##The initial password of Harbor admin, only works for the first time when Harbor starts.
-
#It has no effect after the first launch of Harbor.
-
#Change the admin password from UI after launching Harbor.
-
harbor_admin_password = Weinong$2017
-
-
##By default the auth mode is db_auth, i.e. the credentials are stored in a local database.
-
#Set it to ldap_auth if you want to verify a user's credentials against an LDAP server.
-
auth_mode = db_auth
-
-
#The url for an ldap endpoint.
-
ldap_url = ldaps://ldap.mydomain.com
-
-
#A user's DN who has the permission to search the LDAP/AD server.
-
#If your LDAP/AD server does not support anonymous search, you should configure this DN and ldap_search_pwd.
-
#ldap_searchdn = uid=searchuser,ou=people,dc=mydomain,dc=com
-
-
#the password of the ldap_searchdn
-
#ldap_search_pwd = password
-
-
#The base DN from which to look up a user in LDAP/AD
-
ldap_basedn = ou=people,dc=mydomain,dc=com
-
-
#Search filter for LDAP/AD, make sure the syntax of the filter is correct.
-
#ldap_filter = (objectClass=person)
-
-
# The attribute used in a search to match a user, it could be uid, cn, email, sAMAccountName or other attributes depending on your LDAP/AD
-
ldap_uid = uid
-
-
#the scope to search for users, 0-LDAP_SCOPE_BASE, 1-LDAP_SCOPE_ONELEVEL, 2-LDAP_SCOPE_SUBTREE
-
ldap_scope = 2
-
-
#Timeout (in seconds) when connecting to an LDAP Server. The default value (and most reasonable) is 5 seconds.
-
ldap_timeout = 5
-
-
#Verify certificate from LDAP server
-
ldap_verify_cert = true
-
-
#Turn on or off the self-registration feature
-
self_registration = on
-
-
#The expiration time (in minute) of token created by token service, default is 30 minutes
-
token_expiration = 30
-
-
#The flag to control what users have permission to create projects
-
#The default value "everyone" allows everyone to creates a project.
-
#Set to "adminonly" so that only admin user can create project.
-
project_creation_restriction = everyone
-
-
#************************END INITIAL PROPERTIES************************
-
-
#######Harbor DB configuration section#######
-
-
#The address of the Harbor database. Only need to change when using external db.
-
db_host = mysql
-
-
#The password for the root user of Harbor DB. Change this before any production use.
-
db_password = Weinong$2017
-
-
#The port of Harbor database host
-
db_port = 3306
-
-
#The user name of Harbor database
-
db_user = root
-
-
##### End of Harbor DB configuration#######
-
-
#The redis server address. Only needed in HA installation.
-
redis_url =
-
-
##########Clair DB configuration############
-
-
#Clair DB host address. Only change it when using an exteral DB.
-
clair_db_host = postgres
-
-
#The password of the Clair's postgres database. Only effective when Harbor is deployed with Clair.
-
#Please update it before deployment. Subsequent update will cause Clair's API server and Harbor unable to access Clair's database.
-
clair_db_password = password
-
-
#Clair DB connect port
-
clair_db_port = 5432
-
-
#Clair DB username
-
clair_db_username = postgres
-
-
#Clair default database
-
clair_db = postgres
-
-
##########End of Clair DB configuration############
-
-
#The following attributes only need to be set when auth mode is uaa_auth
-
uaa_endpoint = uaa.mydomain.org
-
uaa_clientid = id
-
uaa_clientsecret = secret
-
uaa_verify_cert = true
-
uaa_ca_cert = /path/to/ca.pem
-
-
-
### Docker Registry setting ###
-
#registry_storage_provider can be: filesystem, s3, gcs, azure, etc.
-
registry_storage_provider_name = filesystem
-
#registry_storage_provider_config is a comma separated "key: value" pairs, e.g. "key1: value, key2: value2".
-
#Refer to https://docs.docker.com/registry/configuration/#storage for all available configuration.
- registry_storage_provider_config =
點選(此處)摺疊或開啟
-
version: '2'
-
services:
-
log:
-
image: vmware/harbor-log:v1.4.0
-
container_name: harbor-log
-
restart: always
-
volumes:
-
- /mnt/harbor/log/:/var/log/docker/:z
-
- ./common/config/log/:/etc/logrotate.d/:z
-
ports:
-
- 127.0.0.1:1514:10514
-
networks:
-
- harbor
-
registry:
-
image: vmware/registry-photon:v2.6.2-v1.4.0
-
container_name: registry
-
restart: always
-
volumes:
-
- /mnt/harbor/registry:/storage:z
-
- ./common/config/registry/:/etc/registry/:z
-
networks:
-
- harbor
-
environment:
-
- GODEBUG=netdns=cgo
-
command:
-
["serve", "/etc/registry/config.yml"]
-
depends_on:
-
- log
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "registry"
-
mysql:
-
image: vmware/harbor-db:v1.4.0
-
container_name: harbor-db
-
restart: always
-
volumes:
-
- /mnt/harbor/database:/var/lib/mysql:z
-
networks:
-
- harbor
-
env_file:
-
- ./common/config/db/env
-
depends_on:
-
- log
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "mysql"
-
adminserver:
-
image: vmware/harbor-adminserver:v1.4.0
-
container_name: harbor-adminserver
-
env_file:
-
- ./common/config/adminserver/env
-
restart: always
-
volumes:
-
- /mnt/harbor/config/:/etc/adminserver/config/:z
-
- /mnt/harbor/secretkey:/etc/adminserver/key:z
-
- /mnt/harbor/:/data/:z
-
networks:
-
- harbor
-
depends_on:
-
- log
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "adminserver"
-
ui:
-
image: vmware/harbor-ui:v1.4.0
-
container_name: harbor-ui
-
env_file:
-
- ./common/config/ui/env
-
restart: always
-
volumes:
-
- ./common/config/ui/app.conf:/etc/ui/app.conf:z
-
- ./common/config/ui/private_key.pem:/etc/ui/private_key.pem:z
-
- ./common/config/ui/certificates/:/etc/ui/certificates/:z
-
- /mnt/harbor/secretkey:/etc/ui/key:z
-
- /mnt/harbor/ca_download/:/etc/ui/ca/:z
-
- /mnt/harbor/psc/:/etc/ui/token/:z
-
networks:
-
- harbor
-
depends_on:
-
- log
-
- adminserver
-
- registry
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "ui"
-
jobservice:
-
image: vmware/harbor-jobservice:v1.4.0
-
container_name: harbor-jobservice
-
env_file:
-
- ./common/config/jobservice/env
-
restart: always
-
volumes:
-
- /mnt/harbor/job_logs:/var/log/jobs:z
-
- ./common/config/jobservice/app.conf:/etc/jobservice/app.conf:z
-
- /mnt/harbor/secretkey:/etc/jobservice/key:z
-
networks:
-
- harbor
-
depends_on:
-
- ui
-
- adminserver
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "jobservice"
-
proxy:
-
image: vmware/nginx-photon:v1.4.0
-
container_name: nginx
-
restart: always
-
volumes:
-
- ./common/config/nginx:/etc/nginx:z
-
networks:
-
- harbor
-
ports:
-
- 80:80
-
- 443:443
-
- 4443:4443
-
depends_on:
-
- mysql
-
- registry
-
- ui
-
- log
-
logging:
-
driver: "syslog"
-
options:
-
syslog-address: "tcp://127.0.0.1:1514"
-
tag: "proxy"
-
networks:
-
harbor:
- external: false
./install.sh
可以使用docker-compose來管理Harbor的生命週期。 一些有用的命令列出如下:
docker-compose ps 檢視
docker-compose stop 停止
docker-compose start 啟動
docker-compose down 刪除,利用./install.sh可以重新安裝
五:驗證
1.碰到的問題
a. 錯誤提示
點選(此處)摺疊或開啟
- /usr/lib/python2.7/site-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.21.1) or chardet (2.2.1) doesn
解決辦法:
pip uninstall urllib3
pip uninstall chardet
pip install requests
b.錯誤提示:“harbor failed to initialize the system: read /etc/adminserver/key: is a directory”
原因:harbor.cfg中的secretkey_path和docker-compose.yml中的設定不一致
2.ui 介面
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28624388/viewspace-2153546/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- kubernetes實踐之二十八:使用Harbor作為私有映象倉庫
- kubernetes實踐之二十九:Kubernetes+Harbor+Gitlab+Jenkins+Maven DevOpsGitlabJenkinsMavendev
- kubernetes實踐之五十七:PodPreset
- kubernetes實踐之十七:架構架構
- kubernetes實踐之二十六:GlusterFS
- kubernetes實踐之二十:網路原理
- kubernetes實踐之二十二:Pod
- kubernetes實踐之二十四:Service
- kubernetes實踐之六十七:Istio介紹
- kubernetes實踐之三十七:Pod健康檢查
- kubernetes實踐之二十三:ReplicationControllerController
- kubernetes實踐之四十七:ResourceQuota ControllerController
- kubernetes實踐之二:建立TLS證書和金鑰TLS
- kubernetes實踐之二十一:物件與元件簡介物件元件
- kubernetes實踐之二十五:儲存卷 PV&PVC
- Kubernetes基於helm安裝 harbor
- Kubernetes監控實踐
- Serverless Kubernetes 落地實踐Server
- Kubernetes Deployment 最佳實踐
- Docker進階與實踐之二:NamespaceDockernamespace
- Kubernetes 微服務最佳實踐微服務
- Kubernetes 最佳安全實踐指南
- kubernetes實踐之十一:EFK
- 基於 Gitlab + Harbor + K8s + Kuboard 的 CI 實踐GitlabK8S
- kubernetes實踐之六十:Cabin-Manage Kubernetes
- kubernetes的Harbor映象私庫線上部署(二)
- 重新整理 .net core 實踐篇——— endpoint[四十七]
- 企業BI實踐系列之二:企業定位
- VPGAME的Kubernetes遷移實踐GAM
- VPGAME 的 Kubernetes 遷移實踐GAM
- 華為雲的Kubernetes實踐之路
- Kubernetes在宜信落地實踐
- kubernetes1.13.X實踐-部署
- Kubernetes YAML最佳實踐和策略YAML
- kubernetes實踐之五十二:Helm
- kubernetes實踐之五十八:CronJob
- kubernetes實踐之三十一:kubectl
- kubernetes實踐之十九:API概述API