From 7da40d20b56cdf1f44e49d34cd94653d7a9ee172 Mon Sep 17 00:00:00 2001 From: Daniel Albuquerque Date: Fri, 23 Sep 2022 10:01:35 +0100 Subject: [PATCH] Update getting-started.md (#253) --- docs/about/getting-started.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/about/getting-started.md b/docs/about/getting-started.md index e0d4e7a..a89f638 100644 --- a/docs/about/getting-started.md +++ b/docs/about/getting-started.md @@ -72,16 +72,21 @@ E.g.: ### File probes Mittens writes files that can be used as liveness and readiness probes. These files are written to disk as `alive` and `ready` respectively. -If you run mittens as a sidecar you can then define a [liveness command](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-liveness-command) as follows: +If you run mittens as a sidecar you can then define [liveness and readiness commands](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) as follows: ``` ... livenessProbe: + exec: + command: + - "cat" + - "alive" +readinessProbe: exec: command: - "cat" - "ready" - ... +... ``` In case such probes are not needed you can disable this feature by setting `file-probe-enabled` to `false`.