178c3044b2
liveness checks are a feature in kubernetes meant to restart hung workloads. Since pebble stores account information in-memory, failing a liveness check means that any running test will fail. Because we're using pebble as part of a testsuite, we're protected against hangs by the test just timing out. On resource constrained environments (like my laptop), I've seen the liveness check fail during startup, causing reboot loops and timeouts. Since rebooting pebble mid-test will cause tests to fail anyhow, we should probably disable this check. Signed-off-by: Daniel Morsing <dmo@jetstack.io> |
||
|---|---|---|
| .. | ||
| chart | ||
| e2e | ||
| fixtures | ||
| unit/gen | ||
| util | ||