From 64c68b61e9949d674a42e206fc8b55e755312e6a Mon Sep 17 00:00:00 2001
From: Martin F <gabel@users.noreply.github.com>
Date: Tue, 2 Oct 2018 08:22:12 +0200
Subject: [PATCH] Added ingress tls values.yaml example to documentation

In the live documentation (mkdocs) the file is hidden. A link only would still hide the content, so adding the content to the docs itself.
---
 docs/examples/tls-termination/README.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/docs/examples/tls-termination/README.md b/docs/examples/tls-termination/README.md
index 849cde1158..a4e20e73b5 100644
--- a/docs/examples/tls-termination/README.md
+++ b/docs/examples/tls-termination/README.md
@@ -8,6 +8,31 @@ You need a [TLS cert](../PREREQUISITES.md#tls-certificates) and a [test HTTP ser
 
 ## Deployment
 
+Create a `values.yaml` file.
+
+```yaml
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+  name: nginx-test
+spec:
+  tls:
+    - hosts:
+      - foo.bar.com
+      # This assumes tls-secret exists and the SSL 
+      # certificate contains a CN for foo.bar.com
+      secretName: tls-secret
+  rules:
+    - host: foo.bar.com
+      http:
+        paths:
+        - path: /
+          backend:
+            # This assumes http-svc exists and routes to healthy endpoints
+            serviceName: http-svc
+            servicePort: 80
+```
+
 The following command instructs the controller to terminate traffic using the provided 
 TLS cert, and forward un-encrypted HTTP traffic to the test HTTP service.