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 2018/11/19 20:33:41 UTC

[GitHub] dgrove-oss opened a new issue #364: Use taints & tolerations for Invoker on multi-node cluster

dgrove-oss opened a new issue #364: Use taints & tolerations for Invoker on multi-node cluster
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/364
 
 
   Enhance the Helm chart and documentation to describe how to use taints and tolerations to prevent any non-OpenWhisk workload that may be deployed onto the same Kubernetes cluster as OpenWhisk from having its pods getting scheduled on an Invoker node.   Since the DockerContainerFactory is completely bypassing the Kubernetes scheduler, we need to cordon off the invoker nodes to protect the OpenWhisk and non-OpenWhisk workloads from each other (the Kubernetes scheduler doesn't have the visibility to do it automatically).
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services