You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2020/03/01 23:33:20 UTC
[GitHub] [openwhisk-deploy-kube] travigd opened a new issue #588: Support
"private" OpenWhisk deployment
travigd opened a new issue #588: Support "private" OpenWhisk deployment
URL: https://github.com/apache/openwhisk-deploy-kube/issues/588
I'm in a situation where I'd like to deploy OpenWhisk for use by other components within a cluster. In particular, I don't really want to expose anything to the public internet, which seems to be impossible with the current setup.
The current options (excluding OpenShift) for `whisk.ingress.type` are `LoadBalancer`, `NodePort`, and `Standard` (which is essentially just a `ClusterIP` service with a "frontend" ingress).
Could we add an option for a `None` ingress (which just creates a ClusterIP service and doesn't create a frontend) or an option to disable the frontdoor ingress (something like `whisk.ingress.frontDoorEnabled` as a boolean)? This might also be useful in setups where the ingress is more complicated and so you want to manage it outside of this chart (e.g., using cloud-provider managed certificates).
I'd be happy to make a PR to add an option to disable frontdoor if that sounds okay (afaict it would be three lines of code plus some documentation).
Thanks for all the awesome work on this!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [openwhisk-deploy-kube] rabbah commented on issue #588: Support
"private" OpenWhisk deployment
Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #588: Support "private" OpenWhisk deployment
URL: https://github.com/apache/openwhisk-deploy-kube/issues/588#issuecomment-593372199
Thanks @travigd! Contributions are welcome.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services