You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ARM 64 node pools. For more information, see [Azure Virtual Machines with ARM-based processors][arm-vms].
71
+
* Windows node pools.
72
+
66
73
## How ImageCleaner works
67
74
68
-
When enabled, an agent is deployed on each agent node, which will use an `ImageList` CRD to determine unreferenced and vulnerable images. An `ImageList` can either be defined manually or automatically generated by ImageCleaner.
75
+
When enabled, an `eraser-controller-manager` pod is deployed on each agent node, which will use an `ImageList` CRD to determine unreferenced and vulnerable images. An `ImageList` can either be defined manually or automatically generated by ImageCleaner.
69
76
70
77
In manual mode, the `ImageList` is created based off of a provided list of image names. In automatic mode, a time interval is set. ImageCleaner will continually run in this interval to generate an updated `ImageList`.
71
78
@@ -83,7 +90,7 @@ In addition to choosing between manual and automatic mode, there are several opt
83
90
84
91
## Enable ImageCleaner on your AKS cluster
85
92
86
-
####Enable ImageCleaner on your cluster
93
+
### Enable ImageCleaner on your cluster
87
94
88
95
To create a new AKS cluster using the default interval, use [az aks create][az-aks-create]:
89
96
@@ -103,6 +110,7 @@ The `--image-cleaner-interval-hours` parameter can be specified at creation time
103
110
104
111
```azurecli-interactive
105
112
az aks update -g MyResourceGroup -n MyManagedCluster \
113
+
--enable-image-cleaner \
106
114
--image-cleaner-interval-hours 48
107
115
```
108
116
@@ -134,3 +142,5 @@ The deletion logs are stored in the `image-cleaner-kind-worker` pods. You can ch
0 commit comments