« Changelog History


consul v1.0.5 Release Notes

Release Date: 2018-02-07 // about 6 years ago

  • 🚀 NOTE ON SKIPPED RELEASE 1.0.4:

    🚀 We found [GH-3867] after cutting the 1.0.4 release and pushing the 1.0.4 release tag, so we decided to scuttle that release and push 1.0.5 instead with a fix for that issue.

    🔒 SECURITY:

    • ⚡️ dns: Updated DNS vendor library to pick up bug fix in the DNS server where an open idle connection blocks the accept loop. [GH-3859]

    🔋 FEATURES:

    • 👍 agent: Added support for gRPC health checks that probe the standard gRPC health endpoint. [GH-3073]

    👌 IMPROVEMENTS:

    • ⚡️ agent: (Consul Enterprise) The disable_update_check option to disable Checkpoint now defaults to true (this is only in the Enterprise version).
    • 🏗 build: Bumped Go version to 1.9.3. [GH-3837]

    🐛 BUG FIXES:

    • 🛠 agent: (Consul Enterprise) Fixed an issue where the snapshot agent's HTTP client config was being ignored in favor of the HTTP command-line flags.
    • 🛠 agent: Fixed an issue where health checks added to services with tags would cause extra periodic writes to the Consul servers, even if nothing had changed. This could cause extra churn on downstream applications like consul-template or Fabio. [GH-3845]
    • 🔀 agent: Fixed several areas where reading from catalog, health, or agent HTTP endpoints could make unintended mofidications to Consul's state in a way that would cause unnecessary anti-entropy syncs back to the Consul servers. This could cause extra churn on downstream applications like consul-template or Fabio. [GH-3867]
    • 🛠 agent: Fixed an issue where Serf events for failed Consul servers weren't being proactively processed by the RPC router. This would prvent Consul from proactively choosing a new server, and would instead wait for a failed RPC request before choosing a new server. This exposed clients to a failed request, when often the proactive switching would avoid that. [GH-3864]