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
As of Nomad 1.8.1 and even more so in 1.9.0, we've reduced the permissions of the node secret to a limited set of RPCs necessary for the client (see #23304#23838#23910).
Although it seems like many of the remaining RPCs could be scoped to a specific nodes, in practice nodes sometimes need to get data about allocs running on other nodes in the cluster (ex. to do migrations). But we could probably tight up the AllowClientOp operation to allow access only to other nodes in the same node pool.
The text was updated successfully, but these errors were encountered:
As of Nomad 1.8.1 and even more so in 1.9.0, we've reduced the permissions of the node secret to a limited set of RPCs necessary for the client (see #23304 #23838 #23910).
Although it seems like many of the remaining RPCs could be scoped to a specific nodes, in practice nodes sometimes need to get data about allocs running on other nodes in the cluster (ex. to do migrations). But we could probably tight up the
AllowClientOp
operation to allow access only to other nodes in the same node pool.The text was updated successfully, but these errors were encountered: