Skip to content

az aks command invoke on private cluster errors with Failed to run command due to cluster perf issue #24192

@kbrkelsi

Description

@kbrkelsi

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    AKSaz aks/acs/openshiftAuto-AssignAuto assign by botServiceThis issue points to a problem in the service.Service AttentionThis issue is responsible by Azure service team.act-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionThis issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions