From e52e6a6fa119683abe593dfca1b5033c7c3f6519 Mon Sep 17 00:00:00 2001 From: Alvaro Neira Ayuso Date: Thu, 7 Nov 2024 13:30:36 +0100 Subject: [PATCH] Include readme section Signed-off-by: Alvaro Neira Ayuso --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 3e3b5dfd67..384053b63c 100644 --- a/README.md +++ b/README.md @@ -60,6 +60,7 @@ original Secret from the SealedSecret. - [How to use kubeseal if the controller is not running within the `kube-system` namespace?](#how-to-use-kubeseal-if-the-controller-is-not-running-within-the-kube-system-namespace) - [How to verify the images?](#how-to-verify-the-images) - [How to use one controller for a subset of namespaces](#How-to-use-one-controller-for-a-subset-of-namespaces) + - [Can I configure the controller retries](#can-i-configure-the-controller-retries) - [Community](#community) - [Related projects](#related-projects) @@ -826,6 +827,10 @@ cosign verify --key .github/workflows/cosign.pub docker.io/bitnami/sealed-secret If you want to use one controller for more than one namespace, but not all namespaces, you can provide additional namespaces using the command line flag `--additional-namespaces=,,<...>`. Make sure you provide appropriate roles and rolebindings in the target namespaces, so the controller can manage the secrets in there. +### Can I configure the Controller retries? + +The answer is yes, you can configure the number of retries in your controller using the flag `--max-retries`. This flag allows you to configure the number of maximum retries to unseal your Sealed Secrets. + ## Community - [#sealed-secrets on Kubernetes Slack](https://kubernetes.slack.com/messages/sealed-secrets)