Edit

Share via

Troubleshooting overview

  • Article

This overview describes how to find solutions for issues you encounter when using Azure Kubernetes Service (AKS) on Azure Local and Windows Server. Known issues and errors topics are organized by functional area. You can use the links provided in this topic to find the solutions and workarounds to resolve them.

For some troubleshooting operations, you may need to use a secure SSH connection to access Windows or Linux worker nodes, which allows you to securely access the nodes for maintenance, log collection, and troubleshooting. For more information, see Connect with SSH to Windows or Linux worker nodes for maintenance and troubleshooting.

View logs to troubleshoot an issue

Logs are an important method to collect and review data from many sources that can provide insights into your environment for troubleshooting purposes. AKS on Azure Local and Windows Server includes some PowerShell cmdlets to collect and view logs, and you can also collect and review kubelet logs.

Find solutions for known issues and errors

AKS on Azure Local and Windows Server troubleshooting topics are organized by functional area. Use the following links to find solutions to issues and errors:

Note

If none of the workarounds found in the links above apply to you, open a support issue.

For issues that are specific to Azure Local, use the following links:

  • Cluster validation reporting in Azure Local: Troubleshoot cluster validation reporting for network and storage QoS (quality of service) settings across servers in an Azure Local and Windows Server cluster.
  • Credential Security Support Provider: Some Azure Local operations use Windows Remote Management (WinRM), which doesn't allow credential delegation by default. To allow delegation, the computer needs to have CredSSP enabled temporarily.

Next steps