This step is in line with the company's competition.
Because the company's environment, we only namespace permissions, but not to manage the entire cluster,
Moreover, the company did not provide a unified helm chart repo,
We can only self.
Reference URL:
http://www.acaiblog.cn/2018/11/13/helm%E6%90%AD%E5%BB%BAchart%E6%9C%AC%E5%9C%B0%E4%BB%93%E5%BA%93/
https://www.hi-linux.com/posts/21466.html
First, install the client helm
# Download Helm $ wget HTTPS: // storage.googleapis.com/kubernetes-helm/helm-v2.9.1-linux-amd64.tar.gz # decompression Helm $ tar . -Zxvf Helm-v2 9.1 . -Linux AMD64- tar .gz # copy the client executable file to the bin directory $ cp Linux-AMD64 / Helm / usr / local / bin /
Second, initialization
Each company under the name seems to have been a tiller installation space, so initialization, not like the new cluster like to skip-refresh, and to specify the tiller-namespaces.
helm init --service-account tiller --tiller-image hub.yun.xxx.com.cn/helm/tiller:v2.7.2 --tiller-namespace myname --skip-refresh
Third, remove the default repo
helm repo remove stable
Fourth, the local repository start a helm
helm serve &
Fifth, create a chart
helm create mychart
Sixth, content editing chart
Seven, the application package to the local warehouse
helm package mychart
Eight, update helm repo
helm repo update
Nine, to view the contents of the local repository
We can only check the specified namespace, so when using the helm commands, or bring --tiller-namespace the tail, or exportr TILLER_NAMESPACE = myname. Relatively once and for all.
helm search
Ten, will be deployed to the cluster chart
Here, to specify namespaces
helm install --debug local/nginx --name nginx-myname --namespace myname
XI, upgrade chart
helm upgrade nginx-myname local/tomcat
Twelve, view historical release
helm history nginx-myname
XIII, specify the version rollback
helm rollback nginx-myname 2