From fa5973a4c42d577143c17222e4d4e962ec8bf6ff Mon Sep 17 00:00:00 2001
From: Chris Kim <30601846+Oats87@users.noreply.github.com>
Date: Fri, 6 Sep 2019 11:08:45 -0700
Subject: [PATCH] Add NLB Disclaimer

Add disclaimer that we do not support NLB terminating TLS connections
---
 .../v2.x/en/installation/ha/create-nodes-lb/nlb/_index.md        | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/nlb/_index.md b/content/rancher/v2.x/en/installation/ha/create-nodes-lb/nlb/_index.md
index b5d4f4fcdf7..88b58cdc056 100644
--- a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/nlb/_index.md
+++ b/content/rancher/v2.x/en/installation/ha/create-nodes-lb/nlb/_index.md
@@ -18,6 +18,7 @@ Configuring an Amazon NLB is a multistage process. We've broken it down into mul
 
 	Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
 
+> **Note:** Rancher only supports using the Amazon NLB when terminating traffic in `tcp` mode for port 443 rather than `tls` mode. This is due to the fact that the NLB does not inject the correct headers into requests when terminated at the NLB. This means that if you want to use certificates managed by the Amazon Certificate Manager (ACM), you should use an ELB or ALB.
 
 ## Create Target Groups