If you have an issue running kubectl commands where the command fails or is slow to respond but you do not recieve any helpful feedback in diagnosing your issue, consider the -v=9 flag to increase kubectl verbosity.
You can see a full breakdown of what each verbosity level from 1 to 9 achieves in the link below, but it might make sense to go right to -v=9 first to see if anything helpful is being reported.
https://kubernetes.io/docs/reference/kubectl/_print/#kubectl-output-verbosity-and-debugging
For example, an issue of file permissions on the local host you are running kubectl from may not be apparent, but running kubectl get all -v=9 may reveal messages such as "failed to write cache to" with the location of the offending file.
Increasing kubectl verbosity to identify issues
