This is an automated email from the ASF dual-hosted git repository. dgrove pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git
commit 1ef8e235809001a34c91daeebe9821fbdf96ea79 Author: David Grove <[email protected]> AuthorDate: Wed Mar 25 09:13:30 2020 -0400 remove trailing whitespace --- docs/k8s-aws.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/k8s-aws.md b/docs/k8s-aws.md index 1c8c8ba..b73e868 100644 --- a/docs/k8s-aws.md +++ b/docs/k8s-aws.md @@ -91,7 +91,7 @@ errors from `wsk` when attempting to access it. Due to the way AWS supports TLS termination on ELBs there are a couple of configuration options required to put a signed certificate in place when deploying openwhisk. -First ensure you have a signed certificate in your AWS Certificate Manager. +First ensure you have a signed certificate in your AWS Certificate Manager. Then ensure you enable the following: ```yaml @@ -105,8 +105,8 @@ whisk: service.beta.kubernetes.io/aws-load-balancer-ssl-cert: <your certificate ARN> ``` -This will setup a loadbalanced service that allows your users to connect via HTTPS to the cluster. Internally we switch -from SSL to plain HTTP communication as we're forwarding ports internally. +This will setup a loadbalanced service that allows your users to connect via HTTPS to the cluster. Internally we switch +from SSL to plain HTTP communication as we're forwarding ports internally. Please read [this doc](https://kubernetes-on-aws.readthedocs.io/en/latest/user-guide/tls-termination.html#common-pitfalls) for more information. ## Hints and Tips
