You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a new(ish) feature of OpenWhisk to support dedicated invokers (apache/openwhisk#5292), that is, the ability to specify an invoker (or invokers) to handle all activations made in a namespace
Use-cases for this could be heterogeneous invoker nodes, and in this case you'd need the ability to ensure an invoker is deployed on a specific node, and that invoker is labelled correctly with the dedicated tag and the dedicatedNamespace label.
I am not sure of the best way to implement this feature in the current helm format, so I ignored this feature in my latest PR #729 because I wanted to get the PR out in a timely fashion.
I am hoping we can have discussion here to figure out how best to integrate this feature as I believe it would be a very useful in the context of Kubernetes deployments.
The text was updated successfully, but these errors were encountered:
There is a new(ish) feature of OpenWhisk to support dedicated invokers (apache/openwhisk#5292), that is, the ability to specify an invoker (or invokers) to handle all activations made in a namespace
Use-cases for this could be heterogeneous invoker nodes, and in this case you'd need the ability to ensure an invoker is deployed on a specific node, and that invoker is labelled correctly with the dedicated tag and the dedicatedNamespace label.
I am not sure of the best way to implement this feature in the current helm format, so I ignored this feature in my latest PR #729 because I wanted to get the PR out in a timely fashion.
I am hoping we can have discussion here to figure out how best to integrate this feature as I believe it would be a very useful in the context of Kubernetes deployments.
The text was updated successfully, but these errors were encountered: