Open marians opened 3 years ago
Interesting, thanks for reporting! Can you check if other CRDs have the same problem?
Also, please enable verbose logging to make debugging easier. I don't have access to a gs cluster :)
Same problem with other CRDs.
$ k access-matrix resource azureclusteridentities.infrastructure.cluster.x-k8s.io -v=debug
DEBU[0000] Set log-level to debug
ERRO[0005] determine requested resource: no matches for /, Resource=azureclusteridentities.infrastructure.cluster.x-k8s.io
$ k access-matrix resource azureclusteridentities -v=debug
DEBU[0000] Set log-level to debug
DEBU[0000] fetching clusterRoles
DEBU[0000] fetching ClusterRoleBindings
DEBU[0000] Skipping roles and rolebindings because namespace is missing
NAME KIND SA-NAMESPACE LIST CREATE UPDATE DELETE
Admins Group ✔ ✖ ✖ ✖
automation ServiceAccount default ✔ ✖ ✖ ✖
azure-operator-5-5-2 ServiceAccount giantswarm ✔ ✔ ✔ ✔
chart-operator-unique ServiceAccount giantswarm ✔ ✔ ✔ ✔
clusterrole-aggregation-controller ServiceAccount kube-system ✔ ✔ ✔ ✔
default ServiceAccount flux-app ✔ ✔ ✔ ✔
dex ServiceAccount giantswarm ✔ ✔ ✔ ✔
draughtsman ServiceAccount draughtsman ✔ ✔ ✔ ✔
g8s.gollum.westeurope.azure.gigantic.io User ✔ ✔ ✔ ✔
gatekeeper-admin ServiceAccount gatekeeper-system ✔ ✔ ✔ ✔
generic-garbage-collector ServiceAccount kube-system ✔ ✖ ✔ ✔
giantswarm:giantswarm-admins Group ✔ ✔ ✔ ✔
horizontal-pod-autoscaler ServiceAccount kube-system ✔ ✖ ✖ ✖
namespace-controller ServiceAccount kube-system ✔ ✖ ✖ ✔
resourcequota-controller ServiceAccount kube-system ✔ ✖ ✖ ✖
system:kube-controller-manager User ✔ ✖ ✖ ✖
system:masters Group ✔ ✔ ✔ ✔
tiller-giantswarm ServiceAccount kube-system ✔ ✔ ✔ ✔
Only ClusterRoleBindings are considered, because no namespace is given.
In a cluster with a CRD named
Organization
(long name:organizations.security.giantswarm.io
), the following command works fine:However, when I use the full CRD name instead, this happens:
I expected to be able to use the full name, like it's the case with
kubectl get <resource>
.