From e49f28873043b72f8cf6907e6ffa23cb77c5a0bb Mon Sep 17 00:00:00 2001 From: chenhonggc Date: Fri, 1 Jun 2018 07:21:55 +0800 Subject: [PATCH] execute tcp liveness probe instance (#8721) * execute tcp liveness probe instance * fix wrong file reference --- .../configure-liveness-readiness-probes.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md index 750af757b4..8a8768302e 100644 --- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md +++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md @@ -195,6 +195,18 @@ starts. Just like the readiness probe, this will attempt to connect to the `goproxy` container on port 8080. If the liveness probe fails, the container will be restarted. +To try the TCP liveness check, create a Pod: + +```shell +kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/tcp-liveness-readiness.yaml +``` + +After 15 seconds, view Pod events to verify that liveness probes: + +```shell +kubectl describe pod goproxy +``` + ## Use a named port You can use a named