Merge branch 'MicrosoftDocs:main' into client_upgrade

Author: jofergus

AKS-Hybrid/create-daemonsets.md

@@ -44,21 +44,21 @@ You describe a DaemonSet by using a YAML file, and then create it using the `kub
 The following example describes the features of a DaemonSet configuration file using an nginx image:
 
 ```yaml
-apiVersion: apps/v1  
-kind: DaemonSet  
-metadata: 
-      labels: 
-         app: nginx
-      name: example-daemon
-spec:  
+---
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  labels:
+    app: nginx
+  name: example-daemon
+spec:
   template:
-    metadata:
+    metadata: null
     labels:
-             app: nginx
-          spec:  
-    containers:  
-        -name: nginx  
-         image: nginx
+      app: nginx
+containers: null
+name: nginx
+image: nginx
 ```
 
 To view the current state of the DaemonSet, use the `kubectl describe` command (for example, `kubectl describe daemonset example-daemon`).

azure-stack/operator/TOC.yml

@@ -14,6 +14,8 @@
       href: release-notes.md
     - name: Hotfixes
       items:
+      - name: Hotfix 1.2406.1.16
+        href: hotfix-1-2406-1-16.md      
       - name: Hotfix 1.2406.1.15
         href: hotfix-1-2406-1-15.md      
       - name: Hotfix 1.2311.3.62

azure-stack/operator/azure-stack-servicing-policy.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Stack Hub
 description: Learn about the Azure Stack Hub servicing policy and how to keep an integrated system in a supported state.
 author: sethmanheim
 ms.topic: article
-ms.date: 07/23/2024
+ms.date: 10/24/2024
 ms.author: sethm
 ms.lastreviewed: 03/18/2020
 
@@ -46,9 +46,9 @@ Find documentation on how to plan for and manage updates, and how to determine y
 
 For information about a specific update, including how to download it, see the release notes for that update:
 
+- [Azure Stack Hub 2408 update](./release-notes.md?view=azs-2408&preserve-view=true)
 - [Azure Stack Hub 2406 update](./release-notes.md?view=azs-2406&preserve-view=true)
 - [Azure Stack Hub 2311 update](./release-notes.md?view=azs-2311&preserve-view=true)
-- [Azure Stack Hub 2306 update](./release-notes.md?view=azs-2306&preserve-view=true)
 
 ## Hotfixes
 
@@ -78,11 +78,11 @@ You must also have an active support agreement with the hardware partner that ma
 
 Hotfixes aren't considered major update versions. If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. You must update to at least the minimum supported version (N-2) to receive support.
 
-For example, if the most recent update version available is 2406 (N), the two previous update versions were 2311 and 2306, which means both 2311 (N-1) and 2306 (N-2) remain in support. However, the 2301 (and earlier) version is out of support, as 2301 was N-3 when the 2406 update was released. For the current release of Azure Stack Hub, the following versions are considered in support:
+For example, if the most recent update version available is 2408 (N), the two previous update versions were 2406 and 2311, which means both 2406 (N-1) and 2311 (N-2) remain in support. However, the 2306 (and earlier) version is out of support, as 2306 was N-3 when the 2408 update was released. For the current release of Azure Stack Hub, the following versions are considered in support:
 
+- [Azure Stack Hub 2408](./release-notes.md?view=azs-2408&preserve-view=true)
 - [Azure Stack Hub 2406](./release-notes.md?view=azs-2406&preserve-view=true)
 - [Azure Stack Hub 2311](./release-notes.md?view=azs-2311&preserve-view=true)
-- [Azure Stack Hub 2306](./release-notes.md?view=azs-2306&preserve-view=true)
 
 Microsoft software update packages are non-cumulative and require the previous update package and latest hotfix to be installed as a prerequisite. If you decide to defer one or more updates, consider the overall runtime required to update to the latest version.
 

azure-stack/operator/hotfix-1-2406-1-16.md

@@ -0,0 +1,43 @@
+---
+title: Azure Stack Hub hotfix 1.2406.1.16
+description: Summary of Azure Stack Hub hotfix 1.2406.1.16
+author: sethmanheim
+ms.topic: article
+ms.date: 10/24/2024
+ms.author: sethm
+
+---
+
+# Azure Stack Hub hotfix 1.2406.1.16
+
+## Summary
+
+- Fixed an issue to prevent a hotfix from a previous release from showing as an applicable update.
+
+## Fixes rolled up from previous hotfix releases
+
+- Fixed an issue with DNS zone creation in SQL and MySQL resource providers.
+- Fixed an issue in which users were able to create duplicate and external infrastructure DNS zones.
+
+## Hotfix information
+
+To apply this hotfix, you must have version **1.2406.0.08** or later.
+
+> [!IMPORTANT]
+> As outlined in the release notes for the [2406 update](release-notes.md?view=azs-2406&preserve-view=true), make sure that you refer to the update activity checklist on running **Test-AzureStack** (with specified parameters), and resolve any operational issues that are found, including all warnings and failures. Also, review active alerts and resolve any that require action.
+
+## File information
+
+Download the following files. Then, follow the instructions in [Apply updates in Azure Stack](azure-stack-apply-updates.md) to apply this update.
+
+[Download the zip file now](https://azurestackhub.azureedge.net/PR/download/MAS_ProdHotfix_1.2406.1.16/HotFix/AzS_Update_1.2406.1.16.zip).
+
+[Download the hotfix xml file now](https://azurestackhub.azureedge.net/PR/download/MAS_ProdHotfix_1.2406.1.16/HotFix/metadata.xml).
+
+## More information
+
+[Azure Stack Hub update resources](azure-stack-updates.md)
+
+[Apply updates in Azure Stack](azure-stack-apply-updates.md)
+
+[Monitor updates in Azure Stack by using the privileged endpoint](azure-stack-monitor-update.md)

azure-stack/operator/known-issues.md

@@ -3,7 +3,7 @@ title: Azure Stack Hub known issues
 description: Learn about known issues in Azure Stack Hub releases.
 author: sethmanheim
 ms.topic: article
-ms.date: 09/03/2024
+ms.date: 10/24/2024
 ms.author: sethm
 ms.reviewer: rtiberiu
 ms.lastreviewed: 11/30/2023
@@ -20,11 +20,11 @@ This article lists known issues in Azure Stack Hub releases. The list is updated
 
 To access known issues for a different version, use the version selector dropdown above the table of contents on the left.
 
-::: moniker range=">=azs-2306"
+::: moniker range=">=azs-2311"
 > [!IMPORTANT]  
 > Review this article before applying the update.
 ::: moniker-end
-::: moniker range="<azs-2306"
+::: moniker range="<azs-2311"
 > [!IMPORTANT]  
 > If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. You must [update to at least the minimum supported version to receive support](azure-stack-servicing-policy.md#keep-your-system-under-support). 
 ::: moniker-end
@@ -33,6 +33,44 @@ To access known issues for a different version, use the version selector dropdow
 <!------------------- SUPPORTED VERSIONS ------------------->
 <!---------------------------------------------------------->
 
+::: moniker range="azs-2408"
+<!-- ## Update -->
+
+<!-- ## Networking -->
+
+## Compute
+
+### Azure Kubernetes Service on Azure Stack Hub
+
+- Applicable: This issue applies to release 2311 and later.
+- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and will not be released to general availability. If you try to register a new subscription to the **Microsoft.Containerservice** resource provider, the registration stays in the **Registering** state. If you try to create a new managed Kubernetes cluster or access existing managed Kubernetes clusters, you might see the raining cloud error screen.
+- Remediation: Microsoft is aware of the problem and is working on a fix.
+- Occurrence: Common.
+
+<!-- ## Alerts -->
+
+<!-- ## Portal -->
+
+<!-- ## Datacenter integration -->
+
+<!-- ## Storage -->
+
+<!-- ## SQL and MySQL-->
+
+<!-- ## App Service -->
+
+<!-- ## Resource providers -->
+
+<!-- ## Usage -->
+
+<!-- ### Identity -->
+
+<!-- ### Marketplace -->
+
+<!-- ## Event Hubs -->
+
+::: moniker-end
+
 ::: moniker range="azs-2406"
 <!-- ## Update -->
 
@@ -151,45 +189,12 @@ To access known issues for a different version, use the version selector dropdow
 
 ::: moniker-end
 
-::: moniker range="azs-2306"
-<!-- ## Update -->
-
-<!-- ## Networking -->
-
-<!-- ## Compute -->
-
-<!-- ## Alerts -->
-
-<!-- ## Portal -->
-
-<!-- ## Datacenter integration -->
-
-<!-- ## Storage -->
-
-<!-- ## SQL and MySQL-->
-
-## App Service
-
-### Incorrect rotation status after secret rotation of resource provider certificates
-
-- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
-- Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
-- Remediation: None. No impact to your system or workloads.
-- Occurrence: All supported versions of Azure Stack Hub.
-
-<!-- ## Usage -->
-
-<!-- ### Identity -->
-
-<!-- ### Marketplace -->
-
-<!-- ## Event Hubs -->
-
-::: moniker-end
-
 <!------------------------------------------------------------>
 <!------------------- UNSUPPORTED VERSIONS ------------------->
 <!------------------------------------------------------------>
+::: moniker range="azs-2311"
+## 2311 archived known issues
+::: moniker-end
 ::: moniker range="azs-2301"
 ## 2301 archived known issues
 ::: moniker-end
@@ -263,6 +268,6 @@ To access known issues for a different version, use the version selector dropdow
 ## 1802 archived known issues
 ::: moniker-end
 
-::: moniker range="<azs-2306"
+::: moniker range="<azs-2311"
 You can access older versions of Azure Stack Hub known issues in the table of contents on the left side, under the [Resources > Release notes archive](./relnotearchive/known-issues.md). Select the desired archived version from the version selector dropdown in the upper left. These archived articles are provided for reference purposes only and do not imply support for these versions. For information about Azure Stack Hub support, see [Azure Stack Hub servicing policy](azure-stack-servicing-policy.md). For further assistance, contact Microsoft Customer Support Services.
 ::: moniker-end