chore(helm): warn about caching images of the storage backend

Author: plaffitt

README.md

@@ -19,7 +19,7 @@ In v1.3.0, we removed the finalizer `pod.kuik.enix.io/finalizer` from pods that
 To avoid having these pods stuck in `Terminating` state after a delete action or a rolling update, you will need to manually remove the finalizer from these pods once you upgrade to 1.3.0.
 This can be achieved using the following command:
 
-```
+```bash
 kubectl get pods --all-namespaces -l kuik.enix.io/images-rewritten=true -o json | jq '.items[].metadata.finalizers=null' | kubectl replace -f -
 ```
 
@@ -80,6 +80,7 @@ One **controller** watches pods, and when it notices new images, it creates `Cac
 Another **controller** watches these `CachedImage` custom resources, and copies images from source registries to kuik's caching registry accordingly.
 
 Here is what our images look like when using kuik:
+
 ```bash
 $ kubectl get pods -o custom-columns=NAME:metadata.name,IMAGES:spec.containers[*].image
 NAME                   IMAGES
@@ -131,7 +132,6 @@ kube-image-keeper-proxy-54lzk                    1m           19Mi
 
 Refer to the [dedicated documentation](https://github.com/enix/kube-image-keeper/blob/main/docs/metrics.md).
 
-
 ## Installation
 
 1. Make sure that you have cert-manager installed. If not, check its [installation page](https://cert-manager.io/docs/installation/) (it's fine to use the `kubectl apply` one-liner, and no further configuration is required).
@@ -148,6 +148,8 @@ That's it!
 
 Our container images are available across multiple registries for reliability. You can find them on [Github Container Registry](https://github.com/enix/kube-image-keeper/pkgs/container/kube-image-keeper), [Quay](https://quay.io/repository/enix/kube-image-keeper) and [DockerHub](https://hub.docker.com/r/enix/kube-image-keeper).
 
+CAUTION: If you use a storage backend that runs in the same cluster as kuik but in a different namespace, ensure you filter-out the storage backend's pods. Failure to do so may lead to interdependency issues, making it impossible to start both kuik and its storage backend if either encounters an issue.
+
 <!-- VALUES -->
 
 ## Installation with plain YAML files

helm/kube-image-keeper/templates/NOTES.txt

@@ -0,0 +1 @@
+CAUTION: If you use a storage backend that runs in the same cluster as kuik but in a different namespace, ensure you filter-out the storage backend's pods. Failure to do so may lead to interdependency issues, making it impossible to start both kuik and its storage backend if either encounters an issue.