From 6718a32fe433ded9f01eacf2181b6be6be95cd93 Mon Sep 17 00:00:00 2001
From: "Benjamin A. Petersen" <ben@benjaminapetersen.me>
Date: Wed, 27 Mar 2024 17:05:23 -0400
Subject: [PATCH] Site debugging revisions.

---
 site/content/docs/howto/debugging.md | 77 +++++++++++++++++++++++-----
 1 file changed, 65 insertions(+), 12 deletions(-)

diff --git a/site/content/docs/howto/debugging.md b/site/content/docs/howto/debugging.md
index 79c653acb..53c87daf1 100644
--- a/site/content/docs/howto/debugging.md
+++ b/site/content/docs/howto/debugging.md
@@ -17,25 +17,78 @@ The `PINNIPED_DEBUG=true` environment variable can be set to enable additional C
 
 ## Debugging on the Server
 
-To adjust the log level of the server side components of Pinniped (such as the Supervisor, Concierge,
-Impersonation Proxy, etc) edit the `log_level` configuration in your local copy of the Pinniped GitHub 
-repository. Open the `deploy/supervisor/values.yaml` or `deploy/concierge/values.yaml` file and edit: 
+To adjust the log level of either the Pinniped Supervisor or the Pinniped Concierge the log level value must be updated 
+in the appropriate configmap associated with each deployment. 
+
+The `log level` options are as follows: 
+- `info` ("nice to know" information) 
+- `debug` (developer information) 
+- `trace` (timing information)
+- `all` (kitchen sink)
+
+Do not use `trace` or `all` on production systems, as credentials may get logged. When this value is left unset, 
+only warnings and errors are printed. There is no way to suppress warning and error logs.
+
+Choose an update method that corresponds with the original installation method you chose for your cluster. Consult
+[Install Supervisor]({{< ref "../howto/install-supervisor" >}}) or [Install Concierge]({{< ref "../howto/install-concierge" >}})
+for more information.
+
+### Using kapp
+
+To adjust the log level of the Pinniped Supervisor or Concierge using `kapp`, edit the `log_level` in the `values.yaml` files 
+in your local copy of the Pinniped GitHub repository. Open either `deploy/supervisor/values.yaml` or `deploy/concierge/values.yaml` 
+and edit the following line: 
 
 ```yaml
 log_level: "info|debug|trace|all"
 ```
-Then apply your configuration.
+Then apply your configuration via `kapp deploy -f`.
 
-The `log_level` options are as follows: 
-- `info` ("nice to know" information) 
-- `debug` (developer information) 
-- `trace` (timing information)
-- `all` (kitchen sink). 
+### Using kubectl
 
-Do not use `trace` or all on production systems, as credentials may get logged. When this value is left unset, 
-only warnings and errors are printed. There is no way to suppress warning and error logs.
+To adjust the log level of the Pinniped Supervisor or Concierge using `kubectl`, find the configmap on your cluster within
+the namespace of each deployment:
 
-## Clearning session and credential caching by the CLI
+```bash
+# get the concierge config
+kubectl get cm pinniped-concierge-config --namespace concierge --output yaml > cm.concierge.yaml
+# get the supervisor config
+kubectl get cm pinniped-supervisor-static-config --namespace supervisor --output yaml > cm.supervisor.yaml
+```
+
+Edit the yaml files:
+
+```yaml
+# pinniped supervisor config
+kind: ConfigMap
+apiVersion: v1
+metadata:
+  name: pinniped-supervisor-static-config
+  namespace: supervisor
+data:
+  pinniped.yaml: |
+    apiGroupSuffix: pinniped.dev
+    log:
+      level: "info|debug|trace|all"
+    # ...
+---
+# pinniped concierge config
+kind: ConfigMap
+apiVersion: v1
+metadata:
+  name: pinniped-concierge-config
+  namespace: supervisor
+data:
+  pinniped.yaml: |
+    apiGroupSuffix: pinniped.dev
+    log:
+      level: "info|debug|trace|all"
+    # ...
+```
+
+And then apply  your configuration via `kubectl apply -f`.
+
+## Clearing session and credential caching by the CLI
 
 Temporary session credentials such as ID, access, and refresh tokens are stored in:
   - `$HOME/.config/pinniped/sessions.yaml` (macOS/Linux)