Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opposite information provided in one instruction about consul acl bootstrap #20832

Open
EugenKon opened this issue Mar 12, 2024 · 0 comments
Open

Comments

@EugenKon
Copy link

On the page: https://developer.hashicorp.com/consul/tutorials/security/access-control-setup-production
You can see:
image

image

it is not clear should I use deny or allow policy?

Until now I followed this instruction: https://github.com/hashicorp/learn-nomad-cluster-setup
Everything work fine. Then I changed for my consul server and consul client acl.enable to true. And my nomad server do not register itself with Consul. I enabled DEBUG/TRACE and I do not see any error messages regarding failed connection between consul/nomad servers. I tried to follow ACL bootstrap instruction but found that information is a bit confusing.\

It would be awesome if documentation will have links to articles which describes how to troubleshot nomad/consul connection.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant