Skip to content

Commit 12915da

Browse files
Merge pull request #262516 from CocoWang-wql/patch-53
Update image-cleaner.md
2 parents ded4859 + c353a26 commit 12915da

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/aks/image-cleaner.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.author: nickoman
55
author: nickomang
66
ms.topic: article
77
ms.custom: devx-track-azurecli
8-
ms.date: 10/22/2023
8+
ms.date: 01/05/2024
99
---
1010

1111
# Use Image Cleaner to clean up stale images on your Azure Kubernetes Service (AKS) cluster
@@ -188,7 +188,8 @@ kubectl logs -n kube-system <worker-pod-name> -c trivy-scanner
188188
kubectl logs -n kube-system <worker-pod-name> -c remover
189189
```
190190

191-
- when `eraser-aks-xxxxx` was deleted, you can follow these steps to enable the [Azure Monitor add-on](./monitor-aks.md) and use the Container Insights pod log table to view historical pod logs.
191+
- `eraser-aks-xxxxx` pod will be deleted in 10 minutes after work completion. You can follow these steps to enable the [Azure Monitor add-on](./monitor-aks.md) and use the Container Insights pod log table. After that, historical logs will be stored and you can review them even `eraser-aks-xxxxx` is deleted
192+
192193
1. Ensure Azure Monitoring is enabled on your cluster. For detailed steps, see [Enable Container Insights on AKS clusters](../azure-monitor/containers/container-insights-enable-aks.md#existing-aks-cluster).
193194

194195
2. Get the Log Analytics resource ID using the [`az aks show`][az-aks-show] command.

0 commit comments

Comments
 (0)