●Change8

Migrating to Consul Connect v2.0.2

Version v2.0.2 introduces 2 breaking changes. This guide details how to update your code.

Released: 7/8/2026

2
Breaking Changes
2
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

xdsapi-gatewayconnect-proxyarmon/go-metricshashicorp/go-metrics

Breaking Changes

●Issue #1

xds: Returning errors when injecting the L4 intention (RBAC) filter or the mTLS transport socket onto an inbound public listener. This prevents the listener from being served without intention enforcement or mTLS, which might break configurations relying on this behavior.

●Issue #2

deps: Migration of `armon/go-metrics` to `hashicorp/go-metrics` may cause issues if direct imports of the old package were used.

Migration Steps

  1. 1
    If you were relying on listeners being served without intention enforcement or mTLS when L4 intention filter or mTLS transport socket was injected onto an inbound public listener, you must now ensure proper configuration.
  2. 2
    Review imports related to `armon/go-metrics` and update them to use `hashicorp/go-metrics`.

Release Summary

This release focuses on security by upgrading the Alpine base image and dependencies, and introduces Enterprise features for API Gateway extensions. It also fixes an xDS bug related to client certificate emission.

Need More Details?

View the full release notes and all changes for Consul Connect v2.0.2.

View Full Changelog