-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Consul connect service mesh not working with consul 1.4.0 #16186
Comments
Hi @suikast42 can you make sure your Nomad client config is updated to deal with the breaking change Consul made? if you're using TLS gRPC you need to use port 8503 now (or configure the grpc_tls port as 8502 on the Consul side). E.g. in #15360 (comment) |
Thats my nomad server and agent consul config. But the result is still the same. consul{
ssl= true
address = "127.0.0.1:8501"
grpc_address = "127.0.0.1:8503"
# this works only with ACL enabled
allow_unauthenticated= true
ca_file = "{{cluster_intermediate_ca_bundle}}"
cert_file = "{{nomad_cert}}"
key_file = "{{nomad_cert_key}}"
} |
@suikast42 I think you will also need to set |
Excactly that 👍 . It seems working as before now. I close this issue and reopen it if I detect any issue belongs to this. |
Hello ! When do you folks plan a 1.4.5 release to include the fix ? Actually the config field |
Soon @timotheencl! We don't have exact dates but we're starting the process of rolling out an RC for 1.5, then the GA release shortly after that which includes the backport releases. |
Nomad version
v 1.5.0-beta.1
Consul version
v 1.14.4
This issue reported in (#15295) and marked as fixed but still present in nomad 1.5.0-beta.1 with consul 1.14.4. Dowgrade consul to v 1.13.3 and let nomad in v 1.5.0-beta.1 works as expected.
The logging output from consul connect proxy:
The text was updated successfully, but these errors were encountered: