-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
Hello,
I cloned the repo, changed the name of the default namespace to "drill" and the type of environment to 'on-prem'
I changed the the service to use ClusterIP instead of nodePort.
When I run it against the namespace 'drill' I just created, I get:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "zk-role" namespace: "drill" from "": no matches for kind "Role" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "drill-role" namespace: "drill" from "": no matches for kind "Role" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "zk-rb" namespace: "drill" from "": no matches for kind "RoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "drill-rb" namespace: "drill" from "": no matches for kind "RoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first]
when using helm install drill1 drill/
I've found out (not yet fluent in helm) that it is related to the RBAC version (thanks to this fix), because my k8s version uses api v1 and not v1beta1 anymore
After changing the RBAC api version in 4 locations it works.
I don't know yet what is the right 'helm'-way to do that, otherwise I would propose a fix (and switching to v1 is not the solution as some people still uses v1beta1)
FYI:
Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.23.6
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels