Skip to content

Commit 8d6318a

Browse files
committed
add a workaround for halted pod restart
1 parent 14169c2 commit 8d6318a

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

build/localnet/README.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ This guide shows how to deploy a LocalNet using [pocket-operator](https://github
2424
- [Debug with dlv](#debug-with-dlv)
2525
- [k8s LocalNet: Connect to a node debugging server](#k8s-localnet-connect-to-a-node-debugging-server)
2626
- [Configure VSCode debugger](#configure-vscode-debugger)
27-
- [docker-compose based LocalNet](#docker-compose-based-localnet)
2827
- [Debug tests](#debug-tests)
2928
- [Troubleshooting](#troubleshooting)
3029
- [Why?](#why)
@@ -245,7 +244,20 @@ Then you have just to set your breakpoints and start the debugging session (no n
245244

246245
[Watch demo](https://github.com/pokt-network/pocket/assets/231488/3525161f-2098-488a-8f36-8747e40320a6)
247246

248-
### docker-compose based LocalNet
247+
k8s runs liveness and readiness checks will restart the pods that are not responsive. In order to not have the debugging session dropped because of the pod restarting, you have to comment `livenessProbe` and `readinessProbe` sections in `charts/pocket/templates/statefulset.yaml`
248+
249+
```yaml
250+
# Comment this section disable liveness checks for debugging
251+
livenessProbe:
252+
httpGet:
253+
path: /v1/health
254+
port: rpc
255+
# Comment this section disable readiness checks for debugging
256+
readinessProbe:
257+
httpGet:
258+
path: /v1/health
259+
port: rpc
260+
```
249261
250262
### Debug tests
251263

0 commit comments

Comments
 (0)