It also creates a config.lock file which is not getting removed after seg-fault
Config file contains only 1 cluster, regular access to the cluster via kubectl work without any noticable issues.
I actually have no clue yet where to start debugging
Environment:
Kubernetes version (use kubectl version): Client: 1.27, Server 1.23
Cloud provider or configuration: OICD with openunison Tremolo
What happened: I'm getting segmentation fault on
kubectl rbac-tool who-can create clusterrolebinding
What you expected to happen: print out who can create clusterrolebinding
How to reproduce it (as minimally and precisely as possible): not sure
Anything else we need to know?:
It also creates a config.lock file which is not getting removed after seg-fault Config file contains only 1 cluster, regular access to the cluster via
kubectl
work without any noticable issues.I actually have no clue yet where to start debugging
Environment:
kubectl version
): Client: 1.27, Server 1.23