az aks command invoke on private cluster errors with Failed to run command due to cluster perf issue
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62
**Related command**
This command when attempted either in cloudshell or remotely from the latest version - 2.40.0, produces the error (sanitized) "(KubernetesOperationError) Failed to run command due to cluster perf issue, container command-################# in aks-command namespace did not start within 30s on your cluster, retry may helps. If issue persist, you may need to tune your cluster with better performance (larger node/paid tier).
Code: KubernetesOperationError
Message: Failed to run command due to cluster perf issue, container command-################# in aks-command namespace did not start within 30s on your cluster, retry may helps. If issue persist, you may need to tune your cluster with better performance (larger node/paid tier).
**To Reproduce**
run the command after authenticating to private cluster
**Expected behavior**
Expected to run kubectl and helm operations on private cluster
**Environment summary**
az cli 2.40
private aks cluster
Kubernetes RBAC enabled
AKS-managed AAD Enabled
**Additional context**
Contributor guide
Assessment
This issue has not been assessed yet.