From 88d3be685eb08728091bebd1c8277cec85559c47 Mon Sep 17 00:00:00 2001
From: Marvin Blum <6115423+Kugelschieber@users.noreply.github.com>
Date: Mon, 21 Oct 2019 15:13:22 +0200
Subject: [PATCH] Removed example for health check endpoint because it is
 misleading. (#181)

---
 README.md | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/README.md b/README.md
index 4a8e1ec..222fe6e 100644
--- a/README.md
+++ b/README.md
@@ -108,22 +108,6 @@ The method can be used to check readiness and/or liveness of the server. It will
 
 ```GET /health```
 
-#### Example using a Kubernetes deployment
-
-```
-# ...
-readinessProbe:
-  httpGet:
-    path: /health
-    port: 80
-  periodSeconds: 2
-  initialDelaySeconds: 2
-  failureThreshold: 3
-  successThreshold: 1
-livenessProbe:
-  # same as for readinessProbe...
-```
-
 ## Self-hosted
 
 You are encouraged to run your own acme-dns instance, because you are effectively authorizing the acme-dns server to act on your behalf in providing the answer to the challenging CA, making the instance able to request (and get issued) a TLS certificate for the domain that has CNAME pointing to it.