Skip to content

Commit de0d681

Browse files
committed
acrolinx
1 parent 7caadab commit de0d681

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/machine-learning/known-issues/inferencing-updating-kubernetes-compute-appears-to-succeed.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Known issue - Existing Kubernetes compute cannot be updated
2+
title: Known issue - Existing Kubernetes compute can't be updated
33
titleSuffix: Azure Machine Learning
4-
description: Updating a Kubernetes attached compute instance using the az ml attach command appears to succeed but does not.
4+
description: Updating a Kubernetes attached compute instance using the az ml attach command appears to succeed but doesn't.
55
author: s-polly
66
ms.author: scottpolly
77
ms.topic: troubleshooting
@@ -11,9 +11,9 @@ ms.date: 08/04/2023
1111
ms.custom: known-issue
1212
---
1313

14-
# Known issue - Existing Kubernetes compute cannot be update with `az ml compute attach` command
14+
# Known issue - Existing Kubernetes compute can't be update with `az ml compute attach` command
1515

16-
Updating a Kubernetes attached compute instance using the `az ml attach` command appears to succeed but does not.
16+
Updating a Kubernetes attached compute instance using the `az ml attach` command appears to succeed but doesn't.
1717

1818

1919
[!INCLUDE [dev v2](../includes/machine-learning-dev-v2.md)]
@@ -24,11 +24,11 @@ Updating a Kubernetes attached compute instance using the `az ml attach` command
2424

2525
## Symptoms
2626

27-
When running the command `az ml compute attach --resource-group <rgname> --workspace-name <ws name> --type Kubernetes --name <existing attached compute name(aaaaa)> --resource-id "<resource URI>" --namespace <deployment name>`, the Workspace UI will display a success message indicating that the compute update was successful, however the compute will not have changed.
27+
When running the command `az ml compute attach --resource-group <rgname> --workspace-name <ws name> --type Kubernetes --name <existing attached compute name(aaaaa)> --resource-id "<resource URI>" --namespace <deployment name>`, the Workspace UI displays a success message indicating that the compute update was successful, however the compute won't have changed.
2828

2929
## Cause
3030

31-
The `az ml compute attach` command is not currently supported for use with Kubernetes compute. At this time, the CLI v2 and SDK v2 do not allow updating any configuration of an existing Kubernetes compute.
31+
The `az ml compute attach` command isn't currently supported for use with Kubernetes compute. At this time, the CLI v2 and SDK v2 don't allow updating any configuration of an existing Kubernetes compute.
3232

3333

3434
## Next steps

0 commit comments

Comments
 (0)