daisy-ycguo closed pull request #401: Document use of subdomains with standard ingress in ibm-public docs URL: https://github.com/apache/incubator-openwhisk-deploy-kube/pull/401
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/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 ---------------------------------------------------------------- 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
