无法在新创建的GKE集群上初始化头盔(分iller) [英] Unable to initialize helm (tiller) on newly created GKE cluster

问题描述

我刚刚在Google Cloud平台上创建了一个GKE集群.我已安装在云控制台helm中:

I have just created a GKE cluster on Google Cloud platform. I have installed in the cloud console helm :

$ helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

我还创建了必要的serviceaccount和clusterrolebinding对象:

I have also created the necessary serviceaccount and clusterrolebinding objects:

$ cat helm-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: tiller
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tiller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
  - kind: ServiceAccount
    name: tiller
    namespace: kube-system


$ kubectl apply -f helm-rbac.yaml                                                                    

serviceaccount/tiller created
clusterrolebinding.rbac.authorization.k8s.io/tiller created

但是尝试初始化tiller会给我以下错误:

However trying to initialise tiller gives me the following error:

$ helm init --service-account tiller --history-max 300
Error: unknown flag: --service-account

那是为什么?

推荐答案

但是尝试初始化分till会给我以下错误:

However trying to initialise tiller gives me the following error:

错误:未知标志:--service-account

Error: unknown flag: --service-account

那是为什么?

头盔 3 是主要升级. 耕种机组件现在已过时.

Helm 3 is a major upgrade. The Tiller component is now obsolete.

没有命令helm init，因此标记--service-account也被删除了.

There is no command helm init therefore also the flag --service-account is removed.

Helm 3的内部实现已从Helm 2发生了很大变化.最明显的变化是移除了Tiller .

这篇关于无法在新创建的GKE集群上初始化头盔(分iller)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！