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: input/troubleshooting/index.md
+57Lines changed: 57 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,6 +160,63 @@ This section outlines some advanced options for checking links.
160
160
There are no link resources in the namespace
161
161
```
162
162
163
+
164
+
<aid="debug-dump"></a>
165
+
## Creating a Skupper debug tar file
166
+
<!--PROCEDURE-->
167
+
168
+
Create a debug tar file containing diagnostic information about a Skupper site to troubleshoot issues or share with support.
169
+
170
+
The `skupper debug dump` command creates a compressed tarball (`.tar.gz`) containing logs, configurations, and resource status from a site. The output file is named using the pattern `<filename>-<namespace>-<datetime>.tar.gz`. If no filename is provided, it defaults to `skupper-dump`.
171
+
172
+
This procedure applies to both Kubernetes and local system sites.
173
+
174
+
**Procedure**
175
+
176
+
1. Create the debug tar file for a site:
177
+
178
+
```bash
179
+
skupper debug dump
180
+
```
181
+
182
+
Or specify a custom filename:
183
+
184
+
```bash
185
+
skupper debug dump mysite-debug
186
+
```
187
+
188
+
The command creates a file such as `skupper-dump-default-20250526-143022.tar.gz`.
189
+
190
+
2. Extract the tar file to examine its contents:
191
+
192
+
```bash
193
+
mkdir skupper-dump
194
+
tar -xzf skupper-dump-default-20250526-143022.tar.gz -C skupper-dump
195
+
cd skupper-dump
196
+
```
197
+
198
+
3. Check the Skupper and platform versions:
199
+
200
+
-`/versions/kubernetes.yaml` - Kubernetes version (on Kubernetes platforms)
201
+
-`/versions/skupper.yaml` - Versions of Skupper components
202
+
203
+
4. Check the site configuration and ingress:
204
+
205
+
-`/site-namespace/resources/Site-<name>.yaml` - Site specification and status
206
+
-`/site-namespace/resources/RouterAccess-<name>.yaml` - Ingress and access type configured for the site
207
+
208
+
5. Check linking and service configuration:
209
+
210
+
-`/site-namespace/resources/Link-<name>.yaml` - Link status between sites
211
+
-`/site-namespace/resources/Accessgrant-<name>.yaml` - Access grants for tokens
212
+
-`/site-namespace/resources/AccessTokens-<name>.yaml` - Token usage information
213
+
-`/site-namespace/resources/Connector-<name>.yaml` - Connector configuration and status
214
+
-`/site-namespace/resources/Listener-<name>.yaml` - Listener configuration and status
0 commit comments