头盔(openshift):找不到可用的版本名称
头盔(openshift):找不到可用的版本名称,openshift,kubernetes-helm,Openshift,Kubernetes Helm,舵机版本的输出: Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean
舵机版本的输出
:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
$ oc version
oc v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://192.168.99.100:8443
openshift v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
oc版本的输出
:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
$ oc version
oc v1.5.1+7b451fc
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://192.168.99.100:8443
openshift v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
云提供商/平台(AKS、GKE、Minikube等):Openshift
尝试安装此软件包时,我在tiller上收到以下错误消息:
客户:
$ helm install incubator/vault --set vault.dev=false
Error: no available release name found
服务器:
[tiller] 2018/08/01 07:36:22 preparing install for
[storage] 2018/08/01 07:36:22 getting release "awesome-tarsier.v1"
[storage/driver] 2018/08/01 07:36:22 get: failed to get "awesome-tarsier.v1": configmaps "awesome-tarsier.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system": User "system:serviceaccount:kube-system:default" cannot get configmaps in project "kube-system"
[tiller] 2018/08/01 07:36:22 info: generated name awesome-tarsier is taken. Searching again.
[storage] 2018/08/01 07:36:22 getting release "limping-tarsier.v1"
[storage/driver] 2018/08/01 07:36:22 get: failed to get "limping-tarsier.v1": configmaps "limping-tarsier.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system": User "system:serviceaccount:kube-system:default" cannot get configmaps in project "kube-system"
[tiller] 2018/08/01 07:36:22 info: generated name limping-tarsier is taken. Searching again.
[storage] 2018/08/01 07:36:22 getting release "coy-lemur.v1"
[storage/driver] 2018/08/01 07:36:22 get: failed to get "coy-lemur.v1": configmaps "coy-lemur.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system": User "system:serviceaccount:kube-system:default" cannot get configmaps in project "kube-system"
[tiller] 2018/08/01 07:36:22 info: generated name coy-lemur is taken. Searching again.
[storage] 2018/08/01 07:36:22 getting release "dapper-kudu.v1"
[storage/driver] 2018/08/01 07:36:22 get: failed to get "dapper-kudu.v1": configmaps "dapper-kudu.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system": User "system:serviceaccount:kube-system:default" cannot get configmaps in project "kube-system"
[tiller] 2018/08/01 07:36:22 info: generated name dapper-kudu is taken. Searching again.
[storage] 2018/08/01 07:36:22 getting release "kneeling-opossum.v1"
[storage/driver] 2018/08/01 07:36:22 get: failed to get "kneeling-opossum.v1": configmaps "kneeling-opossum.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system": User "system:serviceaccount:kube-system:default" cannot get configmaps in project "kube-system"
[tiller] 2018/08/01 07:36:22 info: generated name kneeling-opossum is taken. Searching again.
[tiller] 2018/08/01 07:36:22 warning: No available release names found after 5 tries
[tiller] 2018/08/01 07:36:22 failed install prepare step: no available release name found
我已经安装了minishift
,并使用管理员用户登录
编辑
我还添加了孵化器存储库:
➜ ~ helm repo list
NAME URL
stable https://kubernetes-charts.storage.googleapis.com
local http://127.0.0.1:8879/charts
incubator http://storage.googleapis.com/kubernetes-charts-incubator
我已经检查过保险库是否可用:
➜ ~ helm search vault
NAME CHART VERSION APP VERSION DESCRIPTION
incubator/kubernetes-vault 0.2.1 0.5.2 The Kubernetes-Vault project allows pods to aut...
incubator/vault 0.12.0 0.10.1 A Helm chart for Vault, a tool for managing sec...
incubator/vaultingkube 0.1.2 0.1.1 vaultingkube takes config maps and secrets stor...
stable/vault-operator 0.1.0 0.1.9 CoreOS vault-operator Helm chart for Kubernetes
incubator/goldfish 0.2.6 0.9.0 A Helm chart for Goldfish - Vault UI
我也尝试过:
➜ ~ helm install incubator/vault --set vault.dev=false --set rbac.create=true
但我得到了同样的信息:
错误:找不到可用的发布名称
这可能是由于私隐升级问题 我的第一个想法是在部署图表时启用rbac。 顺便说一句,你没有提到你是否已经加入了孵化器回购。以防万一你没有:
$ helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
回到部署图表时需要启用rbac的位置:
$ helm install incubator/vault --set vault.dev=false --set rbac.create=true
我发现这非常有助于解释k8s RBAC。首先,您可以从vault添加孵化器
helm repo添加孵化器http://storage.googleapis.com/kubernetes-charts-incubator
现在您可以安装vault了
helm安装孵化器/vault——设置vault.dev=false
完成