Open kcexn opened 9 months ago
I doubt it. IIRC, it is only applied to the ansible-based deployment. To co-locate action pods on the same nodes, we need a k8s-centric way such as labeling nodes and filtering out nodes using such labels at pod creation time, and so on.
I don't think I implemented this at all due to time constraints when I ported over the new scheduler architecture. Here is an issue that I created, hoping someone else would pick up that and related tasks of dedicated invokers: https://github.com/apache/openwhisk-deploy-kube/issues/752
Is there a way to configure invokers with Tags using the helm charts?
i.e., as in the tag-based-scheduling in OpenWhisk.
For instance I was thinking of adding user-action pod templates with pod topology constraints to co-locate user-action pods in the same availability zone as its corresponding Invoker when possible. I'd like to be able to add tags to this so that I can force actions to be scheduled in specific zones.