Migrating to Consul Connect ent-changelog-1.18.0
Version ent-changelog-1.18.0 introduces 2 breaking changes. This guide details how to update your code.
Released: 12/2/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
telemetry.disable_hostnameservice router config entriesservice resolver config entriesenvoy.config.core.v3.HeaderValueOption.appendenvoy.config.route.v3.HeaderMatcher.safe_regex_matchenvoy.type.matcher.v3.RegexMatcher.google_re2Breaking Changes
●Issue #1
config-entries: Disabling request and idle timeouts using negative values in service router and service resolver config entries is now allowed.
●Issue #2
telemetry: The value of `telemetry.disable_hostname` is now always respected when determining if gauge-type metrics should be prefixed with the hostname, fixing an issue where this was ignored if only the default metric sink was enabled.
Migration Steps
- 1Review the breaking change regarding `telemetry.disable_hostname` if you rely on metric hostname prefixing behavior when using only the default metric sink.
- 2If using experimental DNS features, note that the new implementation will become default in 1.19.
- 3If using Enterprise features, be aware of the new fault injection filter support.
- 4If linking clusters, use the new API/CLI introduced for HCP Consul Central linking.
Release Summary
Version 1.18.0 shares the Consul Enterprise changelog and introduces several new features, including experimental v2 DNS support and HCP linking capabilities, alongside critical security updates.
Need More Details?
View the full release notes and all changes for Consul Connect ent-changelog-1.18.0.
View Full Changelog