Trying to install on a particular namespace with specific RBAC fails

Consul
1

Hi, we have a namespace where a user has admin role on, when we try to install consul on that namespace, it tries to find CRDs from default namespace and looks for cluster scope rights and fails why ? do we have anything to turn this off ?

PS C:\Users\maheshp> helm upgrade --install consul hashicorp/consul --version “1.0.3” -n abc
Release “consul” does not exist. Installing it now.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource CustomResourceDefinition “exportedservices.consul.hashicorp.com” in namespace “”: customresourcedefinitions.apiextensions.k8s.io “exportedservices.consul.hashicorp.com” is forbidden: User “xxx” cannot get resource “customresourcedefinitions” in API group “apiextensions.k8s.io” at the cluster scope

2

Kubernetes CRDs are only supported at cluster scope, so you need to be a cluster admin to install them.

You can’t add CRDs if you only have permissions to admin a namespace.

3

ok, is there a chart to only install the CRDs so that cluster admin could install it and namespace admin could just use it with specific rbac on CRDs ?