Skip to content

Commit 459b60e

Browse files
committed
Add TSG for cluster upgrade
1 parent f5b4582 commit 459b60e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

AKS-Arc/tsg-aksarc-upgrade-issues.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Upgrading the AKSArc cluster. This operation might take a while...
4747

4848
## Possible causes and follow-ups
4949

50-
- The root cause is a recent change introduced in Azure Local version 2503. Under certain conditions, transient or intermittent failures during the Kubernetes upgrade process are not correctly detected or recovered from, leading the cluster state to remain indefinitely in the 'Upgrading' state.
50+
- The root cause's a recent change introduced in Azure Local version 2503. Under certain conditions, if there are transient or intermittent failures during the Kubernetes upgrade process, they're not correctly detected or recovered from. This can cause the cluster state to stay stuck in the 'Upgrading' state.
5151
- You hit this issue if the version of the AKS Arc extension on your custom location - the `hybridaksextension` extension's version is 2.1.211 or 2.1.223. You can run the following command to check the extension version on your cluster:
5252

5353
```azurecli
@@ -59,14 +59,14 @@ az k8s-extension show -g $res.HybridaksExtension.resourceGroup -c $res.ResourceB
5959

6060

6161
## Mitigation
62-
This issue can be resolved by invoking the AKS Arc update call. The `update` command will retrigger the upgrade flow as well. You can invoke the `aksarc update` command with some placeholder parameters. So in this case, you could invoke the update call to enable NFS or SMB drivers if those features are not already enabled. First, check whether any of the features enabled
62+
This issue can be resolved by invoking the AKS Arc update call. The `update` command will retrigger the upgrade flow as well. You can invoke the `aksarc update` command with some placeholder parameters. So in this case, you could invoke the update call to enable NFS or SMB drivers if those features aren't already enabled. First, check whether any of the features enabled
6363

6464
```azurecli
6565
az login --use-device-code --tenant <Azure tenant ID>
6666
az account set -s <subscription ID>
6767
az aksarc show -g <resource_group_name> -n <cluster_name>
6868
```
69-
Check the storage profile setion:
69+
Check the storage profile section:
7070
```json
7171
"storageProfile": {
7272
"nfsCsiDriver": {
@@ -79,7 +79,7 @@ Check the storage profile setion:
7979
}
8080
```
8181

82-
If one of the drivers are disabled, you can enable it using the following command
82+
If one of the drivers is disabled, you can enable it using the following command:
8383

8484
```azurecli
8585
az aksarc update --enable-smb-driver -g <resource_group_name> -n <cluster_name>

0 commit comments

Comments
 (0)