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 2019/10/22 19:18:40 UTC

[GitHub] [openwhisk-deploy-kube] murthychandrappa opened a new issue #541: How to separate workloads in openwhisk?

murthychandrappa opened a new issue #541: How to separate workloads in openwhisk?
URL: https://github.com/apache/openwhisk-deploy-kube/issues/541
 
 
   Hi,
   
   I am able to setup openwhisk on on-prem kubernetes cluster and I would like to offer to some of pilot customers in our organization. Before offering, I would like to create a isolation or logical separation of workloads like in kubernetes we create namespace and can give access to customers to specific namespaces. Basically each customer should have access to only their workloads and should not be able to manage other customer work loads.
   
   I still have day2 operation questions and is there anyone I can setup a call to understand bit more on the openwhisk platform? We have thousands of developers and hundreds of team so would like to make sure openwhisk can support production workloads with high availability.

----------------------------------------------------------------
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