From a18178de2ae87b80358432f47e6e213ce5b89287 Mon Sep 17 00:00:00 2001 From: Noah Kantrowitz Date: Tue, 28 Jul 2020 02:35:18 -0700 Subject: [PATCH] Make the sealedsecrets.bitnami.com/managed annotation value more correct. Annotation values must be strings, and `true` in YAML is a boolean. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9ac5c4865e..b88d870a07 100644 --- a/README.md +++ b/README.md @@ -342,7 +342,7 @@ only change from existing Kubernetes is that the *contents* of the `Secret` are now hidden while outside the cluster. ### Managing existing secrets -If you want `SealedSecret` controller to take management of an existing `Secret` (i.e. overwrite it when unsealing a `SealedSecret` with the same name and namespace), then you have to annotate that `Secret` with the annotation `sealedsecrets.bitnami.com/managed: true` ahead applying the [Usage](#usage) steps. +If you want `SealedSecret` controller to take management of an existing `Secret` (i.e. overwrite it when unsealing a `SealedSecret` with the same name and namespace), then you have to annotate that `Secret` with the annotation `sealedsecrets.bitnami.com/managed: "true"` ahead applying the [Usage](#usage) steps. ### Update existing secrets