Skip to content

Commit 8d1bbcf

Browse files
Merge branch 'MicrosoftDocs:main' into patch-53
2 parents da95431 + 21ff0da commit 8d1bbcf

File tree

2 files changed

+18
-9
lines changed

2 files changed

+18
-9
lines changed

articles/aks/manage-abort-operations.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,24 @@ ms.subservice: aks-nodes
1111

1212
# Terminate a long running operation on an Azure Kubernetes Service (AKS) cluster
1313

14-
Sometimes deployment or other processes running within pods on nodes in a cluster can run for periods of time longer than expected due to various reasons. While it's important to allow those processes to gracefully terminate when they're no longer needed, there are circumstances where you need to release control of node pools and clusters with long running operations using an *abort* command.
14+
Sometimes deployment or other processes running within pods on nodes in a cluster can run for periods of time longer than expected due to various reasons. You can get insight into the progress of any ongoing operation, such as create, upgrade, and scale, using any preview API version after `2024-01-02-preview` using the following az rest command:
15+
16+
```azurecli-interactive
17+
export ResourceID="You cluster ResourceID"
18+
az rest --method get --url "https://management.azure.com$ResourceID/operations/latest?api-version=2024-01-02-preview"
19+
```
20+
21+
This command provides you with a percentage that indicates how close the operation is to completion. You can use this method to get these insights for up to 50 of the latest operations on your cluster. The "percentComplete" attribute denotes the extent of completion for the ongoing operation, as shown in the following example:
22+
23+
```azurecli-interactive
24+
"id": "/subscriptions/26fe00f8-9173-4872-9134-bb1d2e00343a/resourcegroups/testStatus/providers/Microsoft.ContainerService/managedClusters/contoso/operations/fc10e97d-b7a8-4a54-84de-397c45f322e1",
25+
"name": "fc10e97d-b7a8-4a54-84de-397c45f322e1",
26+
"percentComplete": 10,
27+
"startTime": "2024-04-08T18:21:31Z",
28+
"status": "InProgress"
29+
```
30+
31+
While it's important to allow operations to gracefully terminate when they're no longer needed, there are circumstances where you need to release control of node pools and clusters with long running operations using an *abort* command.
1532

1633
AKS support for aborting long running operations is now generally available. This feature allows you to take back control and run another operation seamlessly. This design is supported using the [Azure REST API](/rest/api/azure/) or the [Azure CLI](/cli/azure/).
1734

articles/key-vault/managed-hsm/logging.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -119,14 +119,6 @@ Individual blobs are stored as text, formatted as a JSON. Let's look at an examp
119119
]
120120
```
121121

122-
123-
124-
## Use Azure Monitor logs
125-
126-
You can use the Key Vault solution in Azure Monitor logs to review Managed HSM **AuditEvent** logs. In Azure Monitor logs, you use log queries to analyze data and get the information you need.
127-
128-
For more information, including how to set this up, see [Azure Key Vault in Azure Monitor](../key-vault-insights-overview.md).
129-
130122
## Next steps
131123

132124
- Learn about [best practices](best-practices.md) to provision and use a managed HSM

0 commit comments

Comments
 (0)