This repository is intended for tracking issues with the Azure Kubernetes Service (AKS). This repository is monitored by the AKS product team, and support is provided on a best-effort basis for issues that are reproducible outside of a specific cluster configuration (see Bug Guidance below).

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

Please Note: Do not file issues for AKS-Engine, ACI, or other services on this repository unless it is related to that feature/service and functionality with AKS. For other tools, products and services see:

• AKS-Engine repo
• Virtual Kubelet

• AKS Roadmap: http://aka.ms/aks/roadmap
• AKS Release Notes: https://aka.ms/aks/releasenotes
• AKS Preview Features: https://aka.ms/aks/previewfeatures
• Updates about the service, including new features and new Azure regions: AKS feed in Azure Updates

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

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.

2. 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.