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
I have the correct client version (1.18) set in features. I've tried with both k8s_openapi::api::rbac::v1::{ClusterRoleBinding};
and v1beta1.
I've been able to create other resources (secrets and service accounts). I've also been able to create the same clusterrolebinding from the command line.
I'd like to be able to have it output exactly what the post request is so I can troubleshoot further, but I don't see any way to do that.
The text was updated successfully, but these errors were encountered:
Ah, yeah, that's a Cluster scoped resource. Unfortunately you just have to pick the right Api constructor since there's no way for us to know what type of scope the resource has atm #194.
In the future, you can turn up kube's logging to debug and you'll see api calls logged:
GET https://0.0.0.0:6443/api/v1/services? Body(Empty)
clux
added
api
Api abstraction related
question
Direction unclear; possibly a bug, possibly could be improved.
labels
Mar 26, 2021
I have the correct client version (1.18) set in features. I've tried with both
k8s_openapi::api::rbac::v1::{ClusterRoleBinding}
;and
v1beta1
.I've been able to create other resources (secrets and service accounts). I've also been able to create the same clusterrolebinding from the command line.
I'd like to be able to have it output exactly what the post request is so I can troubleshoot further, but I don't see any way to do that.
The text was updated successfully, but these errors were encountered: