We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 9c2cfc6 commit 818139bCopy full SHA for 818139b
docs/troubleshooting.md
@@ -201,13 +201,13 @@ To obtain remote logs, run:
201
kctf chal debug logs
202
```
203
204
-In addition, you can run any kubectl command as before.
+In addition, you can run any kubectl command as described in the section [Inspecting a Kubernetes Deployment](#inspecting-a-kubernetes-deployment).
205
206
### Restarting or redeploying
207
208
A good first step is to restart the challenge. To do so run:
209
210
-kctf-kubectl rollout restart deployment/chal
+kubectl rollout restart deployment/chal
211
212
Note: To make Kubernetes automatically restart flaky challenges, you should have a healthcheck.
213
0 commit comments