From 4e99010c7c588c9f6865305572e44332a9e29af0 Mon Sep 17 00:00:00 2001
From: Leon Seng <26860216+leonseng@users.noreply.github.com>
Date: Wed, 27 Sep 2023 16:11:52 +1000
Subject: [PATCH] Updated target label for sealed secret controller when
 restoring from backup

Signed-off-by: Leon Seng <26860216+leonseng@users.noreply.github.com>
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 51b3e770cb..f35753a05b 100644
--- a/README.md
+++ b/README.md
@@ -743,7 +743,7 @@ To restore from a backup after some disaster, just put that secrets back before
 
 ```bash
 kubectl apply -f main.key
-kubectl delete pod -n kube-system -l name=sealed-secrets-controller
+kubectl delete pod -n kube-system -l app.kubernetes.io/name=sealed-secrets
 ```
 
 ### Can I decrypt my secrets offline with a backup key?