The principle of helm and how to solve the problems encountered in installing harbor
This article shows you the principle of helm and how to solve the problems encountered in installing harbor. The content is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.
Helm installation and common commands # install helm# download the latest version of the binary installation package locally from the official website: https://github.com/kubernetes/helm/releasestar-zxvf helm-v3.2.1-linux-amd64.tar.gz # extract the package # put the helm instruction in the bin directory mv linux-amd64/helm / usr/bin/helmhelm help # verify # install tiller Restrictions on role permissions here helm init# query charthelm search chart-name# to view details chart details View installed helm list# installation / update / delete / rollback with harbor as column and harbor as column Helm install/upgrade/uninstall/rollback harbor/harborchart installation method-Chart repository (helm install harbor/harbor)-local Chart package (helm install harbor-1.1.1.tgz)-Chart directory (helm install path/to/harbor)-complete URL (helm install https://test.com/charts/harbor- 1.1.1.tgz). Problems encountered in helm installation of harbor
Q: when using "helm install harbor/harbor", the following error is reported
Error: could not find a ready tiller pod
A: check the containers related to tiller to see if all of them are normal, and find an abnormal
Kubectl get pod-A | grep till
Check its related events and find that it is an exception during mirror pull.
Then pull the mirror, replace, and restart the container.
Docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.3docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.3 gcr.io/kubernetes-helm/tiller:v2.16.3docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.3
You can also modify the deployment directly to modify the corresponding image.
Kubectl edit deployments.apps tiller-deploy-n kube-system
Q: using the command "helm install harbor/harbor" to install the Times error is as follows
Error: no available release name found
A: because tiller does not have the correct role permissions
Kubectl create serviceaccount-namespace kube-system tillerkubectl create clusterrolebinding tiller-cluster-rule-clusterrole=cluster-admin-serviceaccount=kube-system:tillerkubectl patch deploy-namespace kube-system tiller-deploy-p'{"spec": {"template": {"spec": {"serviceAccount": "tiller"}'
Q: POD always reports an error when it starts, as follows, PVC, storage-related problems.
Pod has unbound immediate PersistentVolumeClaims
A: look at the "values.yaml" file in chart and find that the value of "storageClassName" is empty, but "DefaultStorageClass" is not specified.
Kubectl get sc
Modify the "storageClass" and deploy it again to running normally.
... Chartmuseum: existingClaim: "" storageClass: "managed-nfs-storage" subPath: "" accessMode: ReadWriteOnce size: 5Gi jobservice: existingClaim: "" storageClass: "managed-nfs-storage".
Be careful
To check the version of the component, I wasted a lot of time on "delete" and "uninstall" because of the version of helm.
The above is the principle of helm and how to solve the problems encountered in installing harbor. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.
