rabbah closed pull request #152: document how to configure fixed port for 
NodePort ingress
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/pull/152
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

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


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to