Repository files navigation

This repository is offered for tracking features and issues with the Azure KubernetesService (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 abest-effort basis for issues that are reproducible outsideof a specific cluster configuration (seeBug 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 seeAzure Support options andAKS Support Policies.

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

• AKS Roadmap:https://aka.ms/aks/roadmap
• AKS Blog:https://aka.ms/aks/blog
• AKS Release Notes:https://aka.ms/aks/release-notes
• AKS Community YouTube:https://www.youtube.com/@theakscommunity
• AKS Public Community Channel:https://twitter.com/theakscommunity
• Updates about the service, including new features and new Azure regions:AKS feed in Azure Updates
• AKS hybrid deployment options:https://aka.ms/aks-hybrid

This project has adopted theMicrosoft Open Source Code of Conduct. For more information see theCode of Conduct FAQ or contactopencode@microsoft.com with any additional questions or comments.

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 templatethat is shown when opening a new issue. At a bare minimum, issues reported onthis repository must:

1. Be reproducible outside of the current cluster

• This means that if you file an issue that would require direct access toyour cluster and/or Azure resources you will be redirected to open an Azuresupport ticket. Microsoft employees may not ask for personal / subscriptioninformation on Github.
  • For example, if your issue is related to custom scenarios such ascustom network devices, configuration, authentication issues related toyour Azure subscription, etc.

2. Contain the following information:

• A good title: Clear, relevant and descriptive - so that a general idea of theproblem 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 theissue/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, andalso allow them to recreate it easily themselves. This section should alsoinclude 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.