From c2406eabada6fa099c81f5af6ceb4b7a898e2eda Mon Sep 17 00:00:00 2001 From: Alaa <16225699+abarqawi@users.noreply.github.com> Date: Wed, 7 May 2025 12:31:32 +0300 Subject: [PATCH 1/4] Update resolve-az-aks-command-invoke-failures.md Addressing github issue https://github.com/Azure/azure-cli/issues/25336 also case from customer --- .../connectivity/resolve-az-aks-command-invoke-failures.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md index bc8ef1adf7..12be87ce24 100644 --- a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md +++ b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md @@ -46,7 +46,12 @@ The operation returns a `Not Found` status because the `command-` pod can't - Resource constraints - Nodes that have a `NotReady` or `SchedulingDisabled` state -- Nodes that have taints that the pod can't tolerate +- Nodes that have taints that the pod can't tolerate ,most likely you will get ```KubernetesPerformanceError``` or ```KubernetesOperationError```. +``` +(KubernetesPerformanceError) Failed to run command due to cluster perf issue, container command-357ebsdfsd342869 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: KubernetesPerformanceError +Message: Failed to run command due to cluster perf issue, container command-357ebc50d40c47a4a247ab6e067d2869 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). +``` - Other causes #### Solution 1: Change the configuration so that you can schedule and run the pod From 78a58583e8903df1b41bece4c4cbceb500a3ff9e Mon Sep 17 00:00:00 2001 From: Alaa <16225699+abarqawi@users.noreply.github.com> Date: Wed, 7 May 2025 14:19:21 +0300 Subject: [PATCH 2/4] Update resolve-az-aks-command-invoke-failures.md --- .../connectivity/resolve-az-aks-command-invoke-failures.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md index 12be87ce24..ae70071694 100644 --- a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md +++ b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md @@ -46,13 +46,15 @@ The operation returns a `Not Found` status because the `command-` pod can't - Resource constraints - Nodes that have a `NotReady` or `SchedulingDisabled` state -- Nodes that have taints that the pod can't tolerate ,most likely you will get ```KubernetesPerformanceError``` or ```KubernetesOperationError```. +- Nodes that have taints that the pod can't tolerate +- Other causes + +Sample Errors ```KubernetesPerformanceError``` or ```KubernetesOperationError```: ``` (KubernetesPerformanceError) Failed to run command due to cluster perf issue, container command-357ebsdfsd342869 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: KubernetesPerformanceError Message: Failed to run command due to cluster perf issue, container command-357ebc50d40c47a4a247ab6e067d2869 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). ``` -- Other causes #### Solution 1: Change the configuration so that you can schedule and run the pod From cb75cf1d4df3722331e145e4003d9cf1bbcab4f1 Mon Sep 17 00:00:00 2001 From: Amanda Zhu Date: Fri, 9 May 2025 14:39:26 +0800 Subject: [PATCH 3/4] editorial changes --- .../resolve-az-aks-command-invoke-failures.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md index ae70071694..8c11a29032 100644 --- a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md +++ b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md @@ -1,8 +1,8 @@ --- title: Resolve az aks command invoke failures description: Resolve az aks command invoke failures in Azure CLI when you try to access a private Azure Kubernetes Service (AKS) cluster. -ms.date: 10/25/2024 -ms.reviewer: chiragpa, andbar, haitch, momajed, v-leedennis, v-weizhu +ms.date: 05/09/2025 +ms.reviewer: chiragpa, andbar, haitch, momajed, albarqaw， v-leedennis, v-weizhu ms.service: azure-kubernetes-service ms.custom: sap:Connectivity, devx-track-azurecli #Customer intent: As an Azure Kubernetes user, I want to resolve az aks command invoke failures in Azure CLI so that I can successfully connect to my private Azure Kubernetes Service (AKS) cluster. @@ -49,8 +49,9 @@ The operation returns a `Not Found` status because the `command-` pod can't - Nodes that have taints that the pod can't tolerate - Other causes -Sample Errors ```KubernetesPerformanceError``` or ```KubernetesOperationError```: -``` +Here are sample error messages for `KubernetesPerformanceError` or `KubernetesOperationError`: + +```output (KubernetesPerformanceError) Failed to run command due to cluster perf issue, container command-357ebsdfsd342869 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: KubernetesPerformanceError Message: Failed to run command due to cluster perf issue, container command-357ebc50d40c47a4a247ab6e067d2869 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). From e42b9ba30e0c3c35f1d6bb7213827759ad260fce Mon Sep 17 00:00:00 2001 From: Amanda Zhu Date: Tue, 13 May 2025 09:10:39 +0800 Subject: [PATCH 4/4] Update ms.date --- .../connectivity/resolve-az-aks-command-invoke-failures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md index 8c11a29032..cf88a6bc51 100644 --- a/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md +++ b/support/azure/azure-kubernetes/connectivity/resolve-az-aks-command-invoke-failures.md @@ -1,7 +1,7 @@ --- title: Resolve az aks command invoke failures description: Resolve az aks command invoke failures in Azure CLI when you try to access a private Azure Kubernetes Service (AKS) cluster. -ms.date: 05/09/2025 +ms.date: 05/13/2025 ms.reviewer: chiragpa, andbar, haitch, momajed, albarqaw， v-leedennis, v-weizhu ms.service: azure-kubernetes-service ms.custom: sap:Connectivity, devx-track-azurecli