From 0a318353e43ebf596ece69bfe373e7e537690827 Mon Sep 17 00:00:00 2001 From: Paul Laffitte Date: Thu, 14 Mar 2024 11:05:38 +0100 Subject: [PATCH] docs: reword caution about filtering storage pods --- README.md | 2 +- helm/kube-image-keeper/templates/NOTES.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 53750afa..38be4b11 100644 --- a/README.md +++ b/README.md @@ -131,7 +131,7 @@ 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. +CAUTION: If you use a storage backend that runs in the same cluster as kuik but in a different namespace, be sure to filter 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. diff --git a/helm/kube-image-keeper/templates/NOTES.txt b/helm/kube-image-keeper/templates/NOTES.txt index 45fac53b..8f5f6b08 100644 --- a/helm/kube-image-keeper/templates/NOTES.txt +++ b/helm/kube-image-keeper/templates/NOTES.txt @@ -1 +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. +CAUTION: If you use a storage backend that runs in the same cluster as kuik but in a different namespace, be sure to filter 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.