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