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
Right now the tecnativa proxy is deployed onto every single node. For small clusters this is probably fine, but we should adapt the logic in the plugin so that it does not deploy the tecnativa proxy onto nodes that are not relevant. Instead it should suffice if we first get the node id that runs the task we want to exec into and then use a placement constraint in the stack to deploy the service only where we need it.
The text was updated successfully, but these errors were encountered:
Right now the tecnativa proxy is deployed onto every single node. For small clusters this is probably fine, but we should adapt the logic in the plugin so that it does not deploy the tecnativa proxy onto nodes that are not relevant. Instead it should suffice if we first get the node id that runs the task we want to exec into and then use a placement constraint in the stack to deploy the service only where we need it.
The text was updated successfully, but these errors were encountered: