You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the problem being that Kubernetes doesn't have a cluster-reader cluster role defined, it's an Openshift addition.
Kubernetes' closest analog is the cluster role view but that's unlikely to work, it seems to lack essential stuff like nodes.
On that thread we figured out a minimal ClusterRole covering exactly what MIQ needs. Though should not call it cluster-reader, better something like management-reader?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.
As reported on http://talk.manageiq.org/t/kubernetes-provider-displays-no-info-because-of-missing-cluster-reader-clusterrole/3569,
the docs only have instructions for setting up
management-infra
account on Openshift, and these don't work as-is for Kubernetes:http://manageiq.org/docs/guides/providers/kubernetes
http://manageiq.org/docs/reference/latest/doc-Managing_Providers/miq/#containers-providers
the problem being that Kubernetes doesn't have a
cluster-reader
cluster role defined, it's an Openshift addition.view
but that's unlikely to work, it seems to lack essential stuff likenodes
.cluster-reader
, better something likemanagement-reader
?The text was updated successfully, but these errors were encountered: