安装 helm tiller monocular

Part reference  https://blog.csdn.net/bbwangj/article/details/81087911

 

Thunder download helm

https://get.helm.sh/helm-v2.14.1-linux-amd64.tar.gz

 

Upload virtual machines to extract the centos

mv helm-v2.14.1-linux-amd64.tar.gz

Move to the bin directory

 

mv linux-amd64/helm /usr/local/bin/helm

 

helm commands available

Ali cloud mirrored to change helm

helm init --client-only --stable-repo-url https://aliacs-app-catalog.oss-cn-hangzhou.aliyuncs.com/charts/
helm repo add incubator https://aliacs-app-catalog.oss-cn-hangzhou.aliyuncs.com/charts-incubator/
helm repo update

Tiller Installation

helm init


View

kubectl get pods -n kube-system|grep tiller

 

Uninstall using the helm reset

Query charts

helm search

 

Replace the warehouse

# First remove the original warehouse
Helm stable repo the Remove
# to add a new warehouse address
Helm repo stable https://kubernetes.oss-cn-hangzhou.aliyuncs.com/charts the Add
# update warehouse
helm repo update


helm init --client-only --stable-repo-url https://kubernetes.oss-cn-hangzhou.aliyuncs.com/charts
helm repo add incubator https://aliacs-app-catalog.oss-cn-hangzhou.aliyuncs.com/charts-incubator/
helm repo update

Use the following command does not accept parameters reminder

# Create a server
helm init --service-account tiller --upgrade -i registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.14.1 --stable-repo-url https: //kubernetes.oss-cn -hangzhou.aliyuncs.com/charts

Ready to use when installed directly docker tried it again, remove the --upgrade, actually successful installation

helm init --service-account tiller -i registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.14.1 --stable-repo-url https://kubernetes.oss-cn-hangzhou.aliyuncs.com/charts

 

Installation comma behind wrong not true nginx

helm install stable/nginx-ingress --set controller.hostNetwork=true,rbac.create=true

nginx-ingress-controller has been processed pending state but does not affect the use of

curl  http://192.168.220.129:32526/healthz  acquisition response 200, other Request 404

This installation was successful

 

Installation monocular 

helm repo add monocular https://helm.github.io/monocular
helm install --name monocular monocular/monocular
[root@node0 html]# helm install --name monocular monocular/monocular
NAME:   monocular
LAST DEPLOYED: Mon Jun 24 16:33:04 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                           DATA  AGE
monocular-monocular-ui-config  2     0s
monocular-monocular-ui-vhost   1     0s

==> v1/Job
NAME                                              COMPLETIONS  DURATION  AGE
monocular-monocular-sync-initial-incubator-s39qj  0/1          0s        0s
monocular-monocular-sync-initial-stable-j4vxr     0/1          0s        0s

==> v1/Pod(related)
NAME                                                    READY  STATUS             RESTARTS  AGE
monocular-mongodb-74f7cdc89-q7tnz                       0/1    ContainerCreating  0         0s
monocular-monocular-chartsvc-7d9898b444-p8wh8           0/1    ContainerCreating  0         0s
monocular-monocular-chartsvc-7d9898b444-pnqjj           0/1    Pending            0         0s
monocular-monocular-chartsvc-7d9898b444-qmltl           0/1    ContainerCreating  0         0s
monocular-monocular-prerender-59f864d595-dw2t6          0/1    Pending            0         0s
monocular-monocular-sync-initial-incubator-s39qj-ksphd  0/1    Pending            0         0s
monocular-monocular-sync-initial-stable-j4vxr-qcm9f     0/1    Pending            0         0s
monocular-monocular-ui-5ddc8578fb-d9nhq                 0/1    Pending            0         0s
monocular-monocular-ui-5ddc8578fb-xp47k                 0/1    Pending            0         0s

==> v1/Secret
NAME               TYPE    DATA  AGE
monocular-mongodb  Opaque  1     0s

==> v1/Service
NAME                           TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)       AGE
monocular-mongodb              ClusterIP  10.1.14.92    <none>       27017/TCP     0s
monocular-monocular-chartsvc   ClusterIP  10.1.49.242   <none>       8080/TCP      0s
monocular-monocular-prerender  NodePort   10.1.29.23    <none>       80:32398/TCP  0s
monocular-monocular-ui         NodePort   10.1.239.226  <none>       80:31353/TCP  0s

==> v1beta1/CronJob
NAME                                          SCHEDULE   SUSPEND  ACTIVE  LAST SCHEDULE  AGE
monocular-monocular-sync-scheduled-incubator  0 * * * *  False    0       <none>         0s
monocular-monocular-sync-scheduled-stable     0 * * * *  False    0       <none>         0s

==> v1beta1/Deployment
NAME                           READY  UP-TO-DATE  AVAILABLE  AGE
monocular-mongodb              0/1    1           0          0s
monocular-monocular-prerender  0/1    1           0          0s
monocular-monocular-ui         0/2    2           0          0s

==> v1beta1/Ingress
NAME                 HOSTS  ADDRESS  PORTS  AGE
monocular-monocular  *      80       0s

==> v1beta2/Deployment
NAME                          READY  UP-TO-DATE  AVAILABLE  AGE
monocular-monocular-chartsvc  0/3    3           0          0s


NOTES:
The Monocular chart sets up an Ingress to serve the API and UI on the same
domain. You can get the address to access Monocular from this Ingress endpoint:

  $ kubectl --namespace default get ingress monocular-monocular

Point your Ingress hosts to the address from the output of the above command:
  - null
  
Visit https://github.com/helm/monocular for more information.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Guess you like

Origin blog.csdn.net/gs80140/article/details/92795989