-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #90 from fcabrera23/ga-announcement
Ga announcement
- Loading branch information
Showing
1 changed file
with
11 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,37 +4,37 @@ | |
|
|
||
| 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 scope of this repository's objectives. | ||
| 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] | ||
| > 02/21/2023 - AKS Edge Essentials is now GA (version 1.0.406.0). | ||
| :warning: **IMPORTANT**: 02/21/2023 - AKS Edge Essentials is now [Generally Available (GA)](https://aka.ms/aks-edge/ga-blog) - [Version 1.0.406.0](). | ||
|
|
||
| ## Important Links | ||
|
|
||
| - AKS Edge Essentials GA Announcement: https://aka.ms/aks-edge/ga-blog | ||
| - AKS Edge Essentials Overview: https://aka.ms/aks-edge/overview | ||
| - AKS Edge Essentials Quickstart: https://aka.ms/aks-edge/quickstart | ||
| - AKS Edge Essentials Release Notes: https://aka.ms/aks-edge/releases | ||
| - AKS Esge Essentials PowerShell Reference: https://aka.ms/aks-edge/reference | ||
| - AKS Edge Essentials PowerShell Reference: https://aka.ms/aks-edge/reference | ||
|
|
||
| ## 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** | ||
|
|
||
| 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. | ||
| 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. | ||
|
|
||
| 1. **Contain the following information** | ||
| 1. **A good title**: Clear, relevant and descriptive - so that a general idea of the problem can be grasped immediately | ||
| 1. **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 | ||
| 1. **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. | ||
| 1. **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. | ||
| 1. **A good title**: Clear, relevant, and descriptive - so that a general idea of the problem can be grasped immediately | ||
| 1. **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 | ||
| 1. **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. | ||
| 1. **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 | ||
| 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](https://cla.opensource.microsoft.com). | ||
|
|
||
| This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). | ||
| For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or | ||
| For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or | ||
| contact [[email protected]](mailto:[email protected]) with any additional questions or comments. | ||