From 9ae6f022fcef0bf1ba5a5e91678eaad0992f8358 Mon Sep 17 00:00:00 2001 From: Dan Date: Fri, 19 Jul 2024 13:27:30 -0400 Subject: [PATCH] Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon --- .../global-default-private-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md index 095a331d5c7..24ec0695113 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md @@ -70,4 +70,4 @@ However, if you create credential secrets outside of the Rancher GUI (using kube For example, if you have a custom private registry named "my-private-registry" and create a secret called "my-reg-creds" for it, apply the `fleet.cattle.io/managed=true` label to this secret. This ensures that your backup process captures this secret providing easy restoration if needed. -By following this guidance, you can ensure that all your private registry credentials are backed up and easily accessible in the event of a restore or migration. +By following this guidance, you can ensure that all of your private registry credentials are backed up and easily accessible in the event of a restore or migration.