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
ClusterRole, by contrast, is a non-namespaced resource. The resources have different names (Role and ClusterRole) because a Kubernetes object always has to be either namespaced or not namespaced; it can't be both.
I noticed this problem because my terraform apply was failing with the logs:
Error: Cluster level resource cannot take namespace
with kubernetes_manifest.stackdriver["ClusterRole/custom-metrics-resource-reader"]
Resources of type 'rbac.authorization.k8s.io/v1, Kind=ClusterRole' cannot have a namespace
Here is the relevant commit when namespace was added to the ClusterRole
The text was updated successfully, but these errors were encountered:
In file adapter_new_resource_model.yaml on line 44
namespace
property is defined in themetadata
of the ClusterRole.From the official documentation:
I noticed this problem because my terraform apply was failing with the logs:
Here is the relevant commit when namespace was added to the ClusterRole
The text was updated successfully, but these errors were encountered: