This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 16%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERG%3C/text%3E%3C/svg%3E)
Hi Guys,
"az aks command invoke" stopped working with below error for all of our clusters across multiple subscriptions.
az aks command invoke --resource-group actual_resource_group --name actual_cluster_name --command "kubectl get ns"
(KubernetesOperationError) Failed to run command due to cluster perf issue, container command-3d0c9dea7b2e4db9b920114f3942bba4 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-3d0c9dea7b2e4db9b920114f3942bba4 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).
Is anyone else experiencing same issue ? It is happening for more than 24 hours for us.
I suspect performance issue error is misleading and underlaying cause could be different.
Tried it with Paid tier SKU for AKS to ensure its not due to being in Free Tier
Issue persist with Paid Tier
(KubernetesOperationError) Failed to run command due to cluster perf issue, container command-7a568a9ef95749a593bab493e6ff310c 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).
Now error has changed to below
(KubernetesOperationError) Failed to run command in managed cluster due to kubernetes failure. details: failed to execute on pod after retry: SPDYExecutor.SentAADToken retry failed: Internal error occurred: error executing command in container: failed to exec in container: failed to create exec "a10f1646d6f276222bb797b7cff0a2d3a8896fc293dc7b475f34161fc364e227": task 1cf1cf5a897831408cdf7b3cab66c8b32affbd8cbf40a9a39c6f3b8afcc85f61 not found: not found
Code: KubernetesOperationError
Message: Failed to run command in managed cluster due to kubernetes failure. details: failed to execute on pod after retry: SPDYExecutor.SentAADToken retry failed: Internal error occurred: error executing command in container: failed to exec in container: failed to create exec "a10f1646d6f276222bb797b7cff0a2d3a8896fc293dc7b475f34161fc364e227": task 1cf1cf5a897831408cdf7b3cab66c8b32affbd8cbf40a9a39c6f3b8afcc85f61 not found: not found
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Thanks for sharing the update.
This issue was a product bug and has been fixed. More details can be found here as shared by the customer https://github.com/Azure/azure-cli/issues/22738: