Skip to content
Switch branches/tags


Failed to load latest commit information.
Latest commit message
Commit time

Azure Kubernetes Service (AKS) issue and feature tracking


This repository is offered for tracking features and issues with the Azure Kubernetes Service (AKS). This repository is monitored by the AKS product team in order to engage with our community and discuss questions, customer scenarios, or feature requests.

Support through issues on this repository is provided on a best-effort basis for issues that are reproducible outside of a specific cluster configuration (see Bug Guidance below). To receive urgent support you must file a support request through official Azure support channels as urgent support is explicitly out of scope of this repository's objectives.

IMPORTANT: For official customer support with response-time SLAs please see Azure Support options and AKS Support Policies.

Do not file issues for AKS-Engine, Virtual-Kubelet, Azure Container Instances, or services on this repository unless it is related to that feature/service and functionality with AKS. For other tools, products and services see the Upstream Azure Compute projects page.

Important links

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

Bug Reports

IMPORTANT: An inability to meet the below requirements for bug reports are subject to being closed by maintainers and routed to official Azure support channels to provide the proper support experience to resolve user issues.

Bug reports filed on this repository should follow the default issue template that is shown when opening a new issue. At a bare minimum, issues reported on this repository must:

  1. Be reproducible outside of the current cluster
  • This means that if you file an issue that would require direct access to your cluster and/or Azure resources you will be redirected to open an Azure support ticket. Microsoft employees may not ask for personal / subscription information on Github.
    • For example, if your issue is related to custom scenarios such as custom network devices, configuration, authentication issues related to your Azure subscription, etc.
  1. Contain the following information:
  • A good title: Clear, relevant and descriptive - so that a general idea of the problem can be grasped immediately
  • Description: Before you go into the detail of steps to replicate the issue, you need a brief description.
    • Assume that whomever is reading the report is unfamiliar with the issue/system in question
  • Clear, concise steps to replicate the issue outside of your specific cluster.
    • These should let anyone clearly see what you did to see the problem, and also allow them to recreate it easily themselves. This section should also include results - both expected and the actual - along with relevant URLs.
  • Be sure to include any supporting information you might have that could aid the developers.
    • This includes YAML files/deployments, scripts to reproduce, exact commands used, screenshots, etc.