Prometheus-operator: cannot create ClusterRole, ClusterRoleBinding

Created on 12 Jun 2017  路  3Comments  路  Source: prometheus-operator/prometheus-operator

What did you do?

minikube start --extra-config=apiserver.Authorization.Mode=RBAC
kubectl create -f bundle.yml

What did you expect to see?

clusterrole "prometheus-operator" created
clusterrolebinding "prometheus-operator" created

What did you see instead? Under which circumstances?

as a ClusterRoleBinding: no kind "ClusterRoleBinding" is registered for version "rbac.authorization.k8s.io/v1beta1"
Error from server (BadRequest): error when creating "prometheus-bundle.yml": ClusterRole in version "v1beta1" cannot be handled as a ClusterRole: no kind "ClusterRole" is registered for version "rbac.authorization.k8s.io/v1beta1"

Environment

macOS Sierra v10.12.5 (16F73)
MacBook Pro (Retina, 13-inch, Early 2015)
  • Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes cluster kind:

minikube

Most helpful comment

Your cluster is a v1.5.1 Kubernetes cluster, RBAC was in v1alpha1. It has been promoted to vbeta1 in Kubernetes v1.6.x (and that was reflected in our manifests), therefore your error. Upgrading your kubectl to v1.6 and using kubectl apply instead of create should transparently convert the version. (or if this is actually just using minikube, then just use a 1.6 cluster)

All 3 comments

Cluster Roles are not supported at Kubernetes 1.5 .
Try to upgrade your minikube to 1.6

Your cluster is a v1.5.1 Kubernetes cluster, RBAC was in v1alpha1. It has been promoted to vbeta1 in Kubernetes v1.6.x (and that was reflected in our manifests), therefore your error. Upgrading your kubectl to v1.6 and using kubectl apply instead of create should transparently convert the version. (or if this is actually just using minikube, then just use a 1.6 cluster)

My bad, I should have passed the flag during minikube start

Was this page helpful?
0 / 5 - 0 ratings