From 732d01f3c81d052641d65f141a7b8fa1374c0c1c Mon Sep 17 00:00:00 2001
From: Ansil H <11064902+ansilh@users.noreply.github.com>
Date: Sat, 25 Apr 2020 17:25:53 +0530
Subject: [PATCH] Added acme.sh as an example.

Added acme.sh as an example to give more clarity on tls.crt file creation.
---
 .../options/helm2/helm-rancher/tls-secrets/_index.md           | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/_index.md b/content/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/_index.md
index 8920125b9f8..403cb958356 100644
--- a/content/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/_index.md
+++ b/content/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/_index.md
@@ -8,6 +8,9 @@ Kubernetes will create all the objects and services for Rancher, but it will not
 
 Combine the server certificate followed by any intermediate certificate(s) needed into a file named `tls.crt`. Copy your certificate key into a file named `tls.key`.
 
+For example, [acme.sh](https://acme.sh) provides server certificate and CA chains in `fullchain.cer` file. 
+This `fullchain.cer` should be renamed to `tls.crt` & certificate key file as `tls.key`.
+
 Use `kubectl` with the `tls` secret type to create the secrets.
 
 ```