You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+46-11Lines changed: 46 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,12 @@
4
4
5
5
This tool is created to solve my personal pain points while debugging an application inside K8s environment. This tool is not written from the perspective of a devops engineer but rather from the perspective of a backend application engineer trying to debug issues with the application in k8s environment. This tool is not created to be used directly with production environments. It expects certain privileges that might not be available in production. The audience for this is specifically developers running dev clusters or local clusters while debugging an application related issue. Any future feature that may be added will respect the above fact and not go beyond that scope. There might be mature tools available already that might have some intersection with the features provided here but most of those tools are devops centric. This tool is primarily application centric.
6
6
7
-
## Features
7
+
**⚠️ Production Warning**
8
+
This tool requires elevated privileges and is intended for development clusters only. Never use in production environments.
8
9
9
-
#### 1. Persistent Log analysis
10
+
## 🚀 Features
11
+
12
+
### 🔍 Persistent Log Analysis
10
13
11
14
**Problem Addressed:**
12
15
Kubernetes does **not** store logs of deleted pods by default. Tools like `kubectl logs` only work for existing pods. Existing solutions (e.g., Loki, Elasticsearch) require complex log aggregation setups.
@@ -18,10 +21,16 @@ k8sdebug runs a daemon to persistently capture logs for all pods in a namespace
18
21
**Usage**
19
22
20
23
```bash
21
-
k8sdebug logs record start -n <namespace>
22
-
```
24
+
# Start recording logs in a namespace
25
+
k8sdebug logs record start -n my-namespace
23
26
24
-
This will start a dameon process that will record logs from all pods in that namespace and persist it on filesystem (by default in /tmp). Later the logs can be analyzed with following command.
0 commit comments