Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
Consul has an Auto-Config feature which allows Consul clients to automatically configure TLS without having to manually manage certs and config files.
In addition to TLS config, other Nomad client config values could be sent to clients via some centralized way.
More research and exploration is needed, but opening this ticket now in case people have ideas, feedback on how Consul's auto config is working, or any other thoughts.
Use-cases
Remove complexity from the process of security Nomad:
Reduce chance of churning during Nomad set up process
Reduce chances of an insecure Nomad cluster going to prod
Reduce necessity of configuration management tooling for client config
Feedback
I am actively looking to discuss this with potential users, so if you would like to chat about client config, pleas book a 30 minute slot using this link or send an email to mnomitch@hashicorp.com
Proposal
Consul has an Auto-Config feature which allows Consul clients to automatically configure TLS without having to manually manage certs and config files.
In addition to TLS config, other Nomad client config values could be sent to clients via some centralized way.
More research and exploration is needed, but opening this ticket now in case people have ideas, feedback on how Consul's auto config is working, or any other thoughts.
Use-cases
Remove complexity from the process of security Nomad:
Feedback
I am actively looking to discuss this with potential users, so if you would like to chat about client config, pleas book a 30 minute slot using this link or send an email to mnomitch@hashicorp.com