Nomad 1.4.3 has been released with important bug fixes and other improvements.
Critical bug fixes:
- Consul 1.14.0 changed the way in which gRPC listeners are configured if you are using TLS. Nomad clients are unable to fingerprint Consul Connect and cannot place Connect-enabled workloads. This is fixed in Nomad 1.4.3 and backported to Nomad 1.3.8 and 1.2.15. If you are using Consul with Nomad, delay upgrading to Consul 1.14.0 until you have upgraded Nomad to 1.4.3 (or Nomad 1.3.8 or 1.2.15). If you are using TLS with Consul gRPC you will need to set the consul.grpc_tls configuration instead of consul.grpc. during the upgrade to Consul 1.14. See the Consul Upgrade Guide for more information.
- Nomad 1.4.0 introduced a keyring used for workload identity and encrypting Nomad Variables. The replication of this keyring had a bug where keys would no longer be replicated after a raft snapshot was restored. This can include whenever a new server is added to the cluster. This bug was fixed in Nomad 1.4.3.
Nomad 1.4.3 also includes performance improvements for nomad eval delete and the eval broker, the ability to upload job specifications in the web UI, and reliability improvements when starting allocations. See the changelog for more.
Along with Nomad 1.4.3 and Nomad Enterprise 1.4.3, we’re also releasing Nomad 1.3.8 and 1.2.15 with backported bug fixes. See the 1.3.8 and 1.2.15 changelogs for more details.
The Nomad Team
1.4.3 Binaries - Nomad v1.4.3 Binaries | HashiCorp Releases
1.4.3 Changelog - https://github.com/hashicorp/nomad/blob/v1.4.3/CHANGELOG.md
1.3.8 Binaries - Nomad v1.3.8 Binaries | HashiCorp Releases
1.3.8 Changelog - https://github.com/hashicorp/nomad/blob/v1.3.8/CHANGELOG.md
1.2.15 Binaries - Nomad v1.2.15 Binaries | HashiCorp Releases
1.2.15 Changelog - https://github.com/hashicorp/nomad/blob/v1.2.15/CHANGELOG.md