Skip to content
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.

Can not install consul-helm by using helm v2.14.0 #178

Closed
dmai-apixio opened this issue May 29, 2019 · 4 comments · Fixed by #188
Closed

Can not install consul-helm by using helm v2.14.0 #178

dmai-apixio opened this issue May 29, 2019 · 4 comments · Fixed by #188
Labels
bug Something isn't working

Comments

@dmai-apixio
Copy link

Hi all,
I used helm v2.13.0 to install consul. Everything worked perfectly. After upgrading helm to newer version v2.14.0

# helm version
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

I got this error.

helm install --name=consul ./consul/consul-helm -f ./consul/staging.yaml
Error: validation failed: error validating "": error validating data: ValidationError(ClusterRole): missing required field "rules" in io.k8s.api.rbac.v1.ClusterRole
@brucedominguez
Copy link

Same issue here. Tried to run the tutorials on Consul and Ambassador ( https://instruqt.com/hashicorp/tracks/sock-shop-tutorial) but get the same issue. Same version of helm (v2.14.0).

@dverbeek84
Copy link

both server-clusterrole.yaml and client-clusterrole.yaml have a if statement block warpping the rules. thay should wrap the whole ClusterRole block.

@devlounge
Copy link

and the ClusterRoleBinding shouln't be created if the ClusterRole isn't

@lkysow
Copy link
Member

lkysow commented Jun 7, 2019

and the ClusterRoleBinding shouln't be created if the ClusterRole isn't

server-clusterrole.yaml and server-clusterrolebinding.yaml both use the same if statement:

{{- if (or (and (ne (.Values.server.enabled | toString) "-") .Values.server.enabled) (and (eq (.Values.server.enabled | toString) "-") .Values.global.enabled)) }}

So there shouldn't be a way for only one of them to be created. Can you help me reproduce what you're seeing?

lkysow added a commit that referenced this issue Jun 7, 2019
Fixes #178. The rules key must always be set, even if it's to be empty.
lkysow added a commit that referenced this issue Jun 8, 2019
Fixes #178. The rules key must always be set, even if it's to be empty.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants