Shulou(Shulou.com)06/01 Report--

This article is about how helm3 installs harbor. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

1. Download and modify

Helm repo add harbor https://helm.goharbor.io

Helm pull harbor/harbor-version 1.2.3

Modify the values.yaml file

2. Installation

Helm install harbor. / harborError: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"

Since I am the latest version of K8s cluster, version "extensions/v1beta1" is not supported. The following modified version is apps.

Grep-irl "extensions/v1beta1" harbor | grep deployment

Grep-irl "extensions/v1beta1" harbor | grep deploy | xargs sed-I's expansion extension of xargs sed-I's expansion extension of V1beta1 incremental appsl and v1millig'

Perform the installation again

The service needs to request a pv, so here we use hostPath to create a pv

ApiVersion: v1kind: PersistentVolumemetadata: name: harbor-pv1spec: capacity: storage: 10Gi volumeMode: Filesystem accessModes:-ReadWriteOnce persistentVolumeReclaimPolicy: Retain hostPath: path: / helm/harbor/pv1

3. Visit the web interface

Using the user password to log in Hu found that he could not log in. If we look at the pod log, we will find that

Kubectl logs harbor-harbor-registry-6f7765fd94-kxt74 Error from server (BadRequest): a container name must be specified for pod harbor-harbor-registry-6f7765fd94-kxt74, choose one of: [registry registryctl]

Because the name in the container is duplicated, you can change it to be consistent.

Kubectl logs harbor-harbor-redis-01:M 18 Dec 02 changes in 0015 08.032 * 10 seconds. Saving...1:M 18 Dec 02 Failed opening the RDB file dump.rdb 08.033 * Background saving started by pid 9797 Background saving started by pid 9797 Background saving started by pid 08.033 # Failed opening the RDB file dump.rdb (in server root dir / var/lib/redis) 08.033 # Background saving error

Due to insufficient pv permissions requested by redis

Kubectl get pvc # check that the bound pv is the path of the host, and then give the permission to 777

Chmod 777 / helm/harbor/pv4/

Kubectl logs harbor-harbor-clair-c9757f6cb-9x8nr {"Event": "could not download Oracle's update list", "Level": "error", "Location": "oracle.go:162", "Time": "2019-12-18 01Fluor54-54.608195" "error": "Get https://linux.oracle.com/oval/com.oracle.elsa-20161292.xml: read tcp 10.244.2.34 u003e23.63.35.142:443 35278 -\ u003e23.63.35.142:443: read: connection reset by peer"} {"Event": "an error occured when fetching update", "Level": "error", "Location": "updater.go:246", "Time": "2019-12-18 01read tcp 54displacement 54.609261", "error": "could not download requested resource" "updater name": "oracle"}

Delete pod and generate it automatically.

Log in again according to the set password. This is admin/admin12345.

Thank you for reading! This is the end of this article on "how to install harbor in helm3". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.