Skip to content

Commit c353a26

Browse files
authored
Update image-cleaner.md
1 parent d38c589 commit c353a26

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/aks/image-cleaner.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -188,8 +188,7 @@ 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.
192-
- `eraser-aks-xxxxx` pod will be deleted in 10 minutes after work completion. To store and view the historical pod logs, 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, logs will be collected and you can review it even `eraser-aks-xxxxx` is deleted
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
193192

194193
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).
195194

0 commit comments

Comments
 (0)