You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-stack/operator/known-issues.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ To access known issues for a different version, use the version selector dropdow
38
38
39
39
- Applicable: This issue applies to release 2408.
40
40
- Cause: An internal failure of Live Update forces the update method to use FRU instead, which significantly extends the overall update period. Due to this issue, each node update takes an additional 5 hours to complete (approximately).
41
-
- Remediation: If you have more than 8 node stamps, it's advised that you delay your updates if possible, until a hotfix/inline fix is released.
41
+
- Remediation: If you have more than eight node stamps, you should delay your updates if possible, until a hotfix/inline fix is released.
42
42
- Occurrence: Common.
43
43
44
44
<!-- ## Networking -->
@@ -48,15 +48,15 @@ To access known issues for a different version, use the version selector dropdow
48
48
### Azure Kubernetes Service on Azure Stack Hub
49
49
50
50
- Applicable: This issue applies to release 2311 and later.
51
-
- 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.
51
+
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't 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.
52
52
- Remediation: Microsoft is aware of the problem and is working on a fix.
53
53
- Occurrence: Common.
54
54
55
55
### A-series VMs deprecated
56
56
57
57
- Applicable: This issue applies to release 2406 and later.
58
58
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
59
-
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
59
+
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
60
60
- Occurrence: Common.
61
61
62
62
<!-- ## Alerts -->
@@ -93,7 +93,7 @@ To access known issues for a different version, use the version selector dropdow
93
93
### Azure Kubernetes Service on Azure Stack Hub
94
94
95
95
- Applicable: This issue applies to release 2311 and later.
96
-
- 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.
96
+
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't 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.
97
97
- Remediation: Microsoft is aware of the problem and is working on a fix.
98
98
- Occurrence: Common.
99
99
@@ -108,7 +108,7 @@ To access known issues for a different version, use the version selector dropdow
108
108
109
109
- Applicable: This issue applies to release 2406 and later.
110
110
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
111
-
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
111
+
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
112
112
- Occurrence: Common.
113
113
114
114
<!-- ## Alerts -->
@@ -145,7 +145,7 @@ To access known issues for a different version, use the version selector dropdow
145
145
### Azure Kubernetes Service on Azure Stack Hub
146
146
147
147
- Applicable: This issue applies to release 2311 and later.
148
-
- 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.
148
+
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't 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.
149
149
- Remediation: Microsoft is aware of the problem and is working on a fix.
0 commit comments