Some senders use noreply emails addresses and it's easy to distinguish them from something useful based on the reply-to header.

Example: replyto:address@example.com

+* Criteria:
+    query: replyto: "address@example.com"
+  Actions:
+    archive
+    never mark as important
+    apply label: spam

http://linux-quirks.blogspot.com/2011/07/how-to-create-gmail-filter-based-on.

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).

When Kapitan is called with kapitan compile --cache is called, a cache file is created in the compiled/ directory. This file contains the hashes of all input values (classes and parameters). Before compiling the catalog, Kapitan can calculate these hashes and compare them to the current ones. If they didn't change, the compilation won't change anything and can be skipped.

.kapitan_cache