Home

Awesome

Azure Kubernetes Services (AKS) Edge Essentials

Overview

This repository is offered for tracking features and issues with the Azure Kubernetes Service (AKS) Edge Essentials. This repository is monitored by the AKS Edge Essentials 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 following our 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 the scope of this repository's objectives.

Important Links

GA Announcementhttps://aka.ms/aks-edge/ga-blog
Overviewhttps://aka.ms/aks-edge/overview
Quickstarthttps://aka.ms/aks-edge/quickstart
Release Noteshttps://aka.ms/aks-edge/releases
PowerShell Referencehttps://aka.ms/aks-edge/reference
Azure Arc Jumpstarthttps://aka.ms/AKSEEJumpstart
Azure Arc Jumpstart Videoshttps://aka.ms/AKSEEVideos

Bug Guidance

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

    If you file an issue requiring 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.

  2. Contain the following information

    1. A good title: Clear, relevant, and descriptive - so that a general idea of the problem can be grasped immediately
    2. Description: Before you go into the detail of steps to replicate the issue, you need a brief description. Assume that whoever is reading the report is unfamiliar with the issue/system in question
    3. Clear, concise steps to replicate the issue outside your specific cluster.These should let anyone clearly see what you did to see the problem and allow them to recreate it easily. This section should also include results - both expected and actual - along with relevant URLs.
    4. 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.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to and actually do, grant us the rights to use your contribution. For details, visit Microsoft CLA Opensource.

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