From 6e23b8985195e05511093073bff8db5c020d5886 Mon Sep 17 00:00:00 2001 From: Luis Pabon Date: Fri, 30 Nov 2018 12:39:19 +0000 Subject: [PATCH] Update README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 984415a..cf66816 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ How you accomplish this will vary from place to place. For instance, my use case * Kubernetes * Kong docker (not kong-ingress) -I have a `LoadBalancer` service pushing traffic into Kong from the outside world. Kong's deployment contains one pod with two containers: Kong (responding on SSL only) and SSL Redirect (responding on HTTP). +I have a `LoadBalancer` service pushing traffic into Kong from the outside world. Kong's deployment contains one pod with two containers: Kong and SSL Redirect. The `LoadBalancer` service simply binds its port 80 to wherever you configure SSL redirect to. ## Whyyyyy I made this little container to get around Kong's inability to upgrade HTTP connections to HTTPS - there are third party plugins for this, but since I run Kong in Kubernetes there's no easy way to add these plugins without needing to re-build the containers and publish them to a container registry.