From d3f09061392c858dec68b58099a3ab3babd3a3b5 Mon Sep 17 00:00:00 2001 From: stephan48 Date: Thu, 20 Apr 2023 23:27:49 +0200 Subject: [PATCH] --- posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn b/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn index df94c19..88ded7b 100644 --- a/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn +++ b/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn @@ -1,6 +1,6 @@ Hi, -when you use fluxcd2 to allow teams/apps to be seperated into namesapces and wanna use Principle of least Privilege/limit to the target namespace, be carefull with the following: +when you use fluxcd2 to allow teams/apps to be seperated into namesapces and wanna use Principle of least Privilege/limit to the target namespace, be careful with the following: * Errors around secrets are masked as "error: data values must be of type string" as per (this discussion)[https://github.com/fluxcd/flux2/discussions/2355] - disable/remove them for testing, otherwhise you can't debug, this is a gross UX issue. -- 2.30.2