This is an automated email from the ASF dual-hosted git repository.
rabbah pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/incubator-openwhisk-deploy-kube.git
The following commit(s) were added to refs/heads/master by this push:
new b19ad4e document how to configure fixed port for NodePort ingress
(#152)
b19ad4e is described below
commit b19ad4ec9fbe8deba791073ed94a4d634ee3d388
Author: David Grove <dgrove-...@users.noreply.github.com>
AuthorDate: Tue Jan 16 14:01:52 2018 -0500
document how to configure fixed port for NodePort ingress (#152)
Fixes #98.
---
kubernetes/ingress/README.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/kubernetes/ingress/README.md b/kubernetes/ingress/README.md
index 3b985c4..82cd40c 100644
--- a/kubernetes/ingress/README.md
+++ b/kubernetes/ingress/README.md
@@ -42,7 +42,10 @@ wsk property set --auth `cat ../cluster-setup/auth.guest`
--apihost API_HOST
When it was deployed, the apigateway and nginx services were
configured to expose themselves via a NodePort
-[see](https://github.com/apache/incubator-openwhisk-deploy-kube/tree/master/kubernetes/cluster-setup/services.yml#L13)
+[see](https://github.com/apache/incubator-openwhisk-deploy-kube/tree/master/kubernetes/cluster-setup/services.yml#L13)
with a dynamically assigned port number. If you want
+a specific port number to be assigned to these services, you can cause
+this to happen by adding a `nodePort:` field to some or all of the [`port:`
+stanzas](https://github.com/apache/incubator-openwhisk-deploy-kube/tree/master/kubernetes/cluster-setup/services.yml#L17-L25)
and redeploying the service.
By determining the IP address of a worker node and the exposed port
numbers, you can determine your API_HOST and APIGW_URL. There are no
additional files to apply. TLS termination is handled by the nginx
--
To stop receiving notification emails like this one, please contact
['"commits@openwhisk.apache.org" <commits@openwhisk.apache.org>'].
