[incubator-openwhisk-deploy-kube] branch master updated: Document use of subdomains with standard ingress in ibm-public docs (#401)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

daisyguo 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 6996b30  Document use of subdomains with standard ingress in ibm-public docs (#401)
6996b30 is described below

commit 6996b306c88da56d6a8d61946b8a4bcfa536fce4
Author: David Grove <dg...@users.noreply.github.com>
AuthorDate: Mon Jan 7 01:16:11 2019 -0500

    Document use of subdomains with standard ingress in ibm-public docs (#401)
    
    Fixes #388.
---
 docs/k8s-ibm-public.md | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/docs/k8s-ibm-public.md b/docs/k8s-ibm-public.md
index 5b3c75d..4fc303c 100644
--- a/docs/k8s-ibm-public.md
+++ b/docs/k8s-ibm-public.md
@@ -36,6 +36,7 @@ Follow IBM's instructions to provision your cluster.
 ####  IBM Cloud Standard cluster
 
 An IBM Cloud Standard cluster has full support for TLS
+including a wild-card certificate for subdomains
 and can be configured with additional annotations to
 fine tune ingress performance.
 
@@ -59,16 +60,23 @@ Ingress secret:  <ibmtlssecret>
 Workers:  3
 ```
 
+As described in [IBM's ingress documentation](https://cloud.ibm.com/docs/containers/cs_ingress.html#ingress),
+to enable applications deployed in multiple namespaces to share the ingress resource,
+you should use a unique subdomain name for each namespace.  We suggest
+a convention of using the namespace name as the subdomain name.  So if you
+are deploying openwhisk into the `openwhisk` namespace, use `openwhisk`
+as your subdomain (as shown below in the example `mycluster.yaml`).
+
 Now define `mycluster.yaml` as below (substituting the real values for
 `<domain>` and `<ibmtlssecret>`).
 ```yaml
 whisk:
   ingress:
-    apiHostName: <domain>
+    apiHostName: openwhisk.<domain>
     apiHostPort: 443
     apiHostProto: https
     type: standard
-    domain: <domain>
+    domain: openwhisk.<domain>
     tls:
       enabled: true
       secretenabled: true