Open suikast42 opened 2 years ago
Hi @suikast42 . Thanks for sharing your experience. I'm glad that you ultimately figured out how to get things working. I'm sorry the documentation wasn't as clear as you hoped. I'll take a look and see if there is something that needs improvement.
Nomad version
Nomad v1.3.5
Cunsul version
Consul v1.13.1
I try out the nomad ( consul ) service mesh capabilities. I try out the counter-dashboard example. Without TLS enabled it works as expected. So it counts :-)
After the first success of deployment I follow the guide for consul security.
After this step the envoy proxy is not able to connect the service. The envoy proxy says:
I use cfssl for generating my certificates and not use the consul provided one. but I try the dasboard example with the ca tool of consul as well. Both results are the same.
After some digging I find a workarround.
The auto_config section define the client cert section as shown below.
But as you can see below, I put there my own generated certificates. and add env vars to the nomad.service systemd file
Without adding the confusing and unessarry cert_file and key_file definition in consul client config I got an error from nomad client
Without adding systemd env vars the proxy is not connecting.
Is something lacking in the docu or did I miss something ?
For a simple acl I use the management token 'e95b599e-166e-7d80-08ad-aee76e7ddf19'
Consul server:
nomad server
Consul client
Nomad client