docs: update logging config (aws#7192)

wesley-yep-canva · Oct 10, 2024 · 9504270 · 9504270
1 parent 55d3322
commit 9504270
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 57 deletions.
diff --git a/website/content/en/docs/troubleshooting.md b/website/content/en/docs/troubleshooting.md
@@ -10,26 +10,9 @@ description: >
 
 ### Enable debug logging
 
-To enable debug logging on Karpenter you should update the `config-logging` ConfigMap which can be found in the same namespace as the controller.
-If you installed the controller in the `karpenter` namespace you can see the current config with
+This can be done by updating the env variable `LOG_LEVEL` Karpenter deployment and then restarting the Karpenter deployment.
 
-```
-kubectl get configmap -n karpenter config-logging -o yaml
-apiVersion: v1
-data:
-  loglevel.webhook: error
-  zap-logger-config: |
-    {
-      "level": debug",
-      development": false,
-...
-```
-
-Update the zap-logger-config "level" and restart the Karpenter pod(s) to enable debug logging.
-
-#### Debug logging via Helm
-
-You can enable debug logging during installation with Helm by setting the option `logLevel`.
+You can also enable debug logging during installation with Helm by setting the option `logLevel`.
 
 ```
 helm upgrade --install karpenter oci://public.ecr.aws/karpenter/karpenter \

diff --git a/website/content/en/preview/troubleshooting.md b/website/content/en/preview/troubleshooting.md
@@ -10,26 +10,9 @@ description: >
 
 ### Enable debug logging
 
-To enable debug logging on Karpenter you should update the `config-logging` ConfigMap which can be found in the same namespace as the controller.
-If you installed the controller in the `karpenter` namespace you can see the current config with
+This can be done by updating the env variable `LOG_LEVEL` Karpenter deployment and then restarting the Karpenter deployment.
 
-```
-kubectl get configmap -n karpenter config-logging -o yaml
-apiVersion: v1
-data:
-  loglevel.webhook: error
-  zap-logger-config: |
-    {
-      "level": debug",
-      development": false,
-...
-```
-
-Update the zap-logger-config "level" and restart the Karpenter pod(s) to enable debug logging.
-
-#### Debug logging via Helm
-
-You can enable debug logging during installation with Helm by setting the option `logLevel`.
+You can also enable debug logging during installation with Helm by setting the option `logLevel`.
 
 ```
 helm upgrade --install karpenter oci://public.ecr.aws/karpenter/karpenter \

diff --git a/website/content/en/v1.0/troubleshooting.md b/website/content/en/v1.0/troubleshooting.md
@@ -10,26 +10,9 @@ description: >
 
 ### Enable debug logging
 
-To enable debug logging on Karpenter you should update the `config-logging` ConfigMap which can be found in the same namespace as the controller.
-If you installed the controller in the `karpenter` namespace you can see the current config with
+This can be done by updating the env variable `LOG_LEVEL` Karpenter deployment and then restarting the Karpenter deployment.
 
-```
-kubectl get configmap -n karpenter config-logging -o yaml
-apiVersion: v1
-data:
-  loglevel.webhook: error
-  zap-logger-config: |
-    {
-      "level": debug",
-      development": false,
-...
-```
-
-Update the zap-logger-config "level" and restart the Karpenter pod(s) to enable debug logging.
-
-#### Debug logging via Helm
-
-You can enable debug logging during installation with Helm by setting the option `logLevel`.
+You can also enable debug logging during installation with Helm by setting the option `logLevel`.
 
 ```
 helm upgrade --install karpenter oci://public.ecr.aws/karpenter/karpenter \