docs(readme): mention the fact that kuik ignore its own namespace

README.md

@@ -64,7 +64,7 @@ Another **controller** watches these `CachedImage` custom resources, and copies
 
 Here is what our images look like when using kuik:
 ```bash
-$ kubectl get pods -o custom-columns=NAME:metadata.name,IMAGES:spec.containers[*].image 
+$ kubectl get pods -o custom-columns=NAME:metadata.name,IMAGES:spec.containers[*].image
 NAME                   IMAGES
 debugger               localhost:7439/registrish.s3.amazonaws.com/alpine
 factori-0              localhost:7439/factoriotools/factorio:1.1
@@ -101,11 +101,11 @@ The image cache will obviously require a bit of disk space to run (see [Garbage
 
 ```bash
 $ kubectl top pods
-NAME                                             CPU(cores)   MEMORY(bytes)   
-kube-image-keeper-0                              1m           86Mi            
-kube-image-keeper-controllers-5b5cc9fcc6-bv6cp   1m           16Mi            
-kube-image-keeper-controllers-5b5cc9fcc6-tjl7t   3m           24Mi            
-kube-image-keeper-proxy-54lzk                    1m           19Mi            
+NAME                                             CPU(cores)   MEMORY(bytes)
+kube-image-keeper-0                              1m           86Mi
+kube-image-keeper-controllers-5b5cc9fcc6-bv6cp   1m           16Mi
+kube-image-keeper-controllers-5b5cc9fcc6-tjl7t   3m           24Mi
+kube-image-keeper-proxy-54lzk                    1m           19Mi
 ```
 
 ![Architecture](./docs/architecture.jpg)
@@ -158,7 +158,7 @@ helm upgrade --install \
      --set cachedImagesExpiryDelay=90
 ```
 
-## Advanced usage 
+## Advanced usage
 
 ### Pod filtering
 
@@ -170,6 +170,8 @@ There are 3 ways to tell kuik which pods it should manage (or, conversely, which
 
 This logic isn't implemented by the kuik controllers or webhook directly, but through Kubernetes' standard webhook object selectors. In other words, these parameters end up in the `MutatingWebhookConfiguration` template to filter which pods get presented to kuik's webhook. When the webhook rewrites the images for a pod, it adds a label to that pod, and the kuik controllers then rely on that label to know which `CachedImages` resources to create.
 
+Keep in mind that kuik will ignore pods scheduled into its own namespace.
+
 ### Cache persistence & garbage collection
 
 Persistence is disabled by default. You can enable it by setting the Helm value `registry.persistence.enabled=true` and setting `registry.persistence.size` to the desired size (20 GiB by default). Be aware that this don't allow for high availability of the registry, to enable HA please refer to our related guide [./docs/high-availability.md](./docs/high-availability.md).