We have successfully enabled the ACL subsystem on our Nomad cluster by setting acl.enabled = true
for all the Nomad servers on the cluster. It appears that the ACL works as expected without needing to set acl.enabled = true
for the Nomad clients on the cluster.
The Nomad ACL docs do mention enabling ACL’s on Nomad clients:
To enforce client endpoints, you need to enable ACLs on clients as well. Do this by setting the enabled value of the acl stanza to true. Once complete, restart the client to read in the new configuration.
However, what we've seen is that Nomad CLI commands run from a client (without acl.enabled = true
) are still gated with 403 (Permission Denied), as expected.
As our cluster has many clients, it would save us time if we did not have to explicitly enable ACL for every client.
To summarize - we would like to know if it is absolutely required that the Nomad clients also have their configuration updated to enable ACL, even though the ACL subsystem appears to already work by just enabling ACL on the Nomad servers.