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
Copy file name to clipboardexpand all lines: docs/policies.md
+9-2
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,10 @@ five of tags which were previously marked for deletion since they don't fulfil t
27
27
28
28
In a sense the `Requirement` policies are stronger than the `Target` policies.
29
29
30
+
> [!IMPORTANT]
31
+
> A rule with only `Requirement` policies without any `Target` policies doesn't match anything since the `Requirement` policies are only used to filter the matches of the
32
+
> `Target` policies and not for matching itself
33
+
30
34
## Tag policies
31
35
32
36
Tag policies are used to determine which tags on an image should be marked for deletion
@@ -38,10 +42,13 @@ Tag policies are used to determine which tags on an image should be marked for d
38
42
>
39
43
> Default: `15`
40
44
41
-
The revision policy aims to only keep a specified amount of tags for an image in the registry. In combination with other
42
-
policies it can be less than the specified amount of tags is kept. When there are more tags than specified in the policy it
45
+
The revision policy aims to only keep a specified amount of tags for an image in the registry. When there are more tags than specified in the policy it
43
46
marks the excess ones for deletion. The tags are marked for deletion from oldest to newest (by creation date).
44
47
48
+
> [!IMPORTANT]
49
+
> When used with other tag policies the real revision count can be higher than the specified value since there could be the case
50
+
> where tags which would be deleted by the revision policy are filtered out by a policy of type `Requirement` which retains them from being deleted
0 commit comments