●Change8

Migrating to Consul Connect ent-changelog-1.11.0

Version ent-changelog-1.11.0 introduces 2 breaking changes. This guide details how to update your code.

Released: 12/2/2025

2
Breaking Changes
2
Migration Steps
15
Affected Symbols

⚠️ Check Your Code

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

consul acl set-agent-token masterconsul acl set-agent-token recoveryagent health and maintenance endpoints (API)consul config delete commandconnect/ca (x509 non-CA certificates)Ingress (Connect)service-resolver subset filters (Connect)Envoy (Connect)/v1/agent/metrics/stream (API)cluster capture target (debug API)DNS virtual endpointHTTP API path handling (404 responses)boltdb (Raft)iptable rules (SDK)serf_lan_allowed_cidrs (Segments)

Breaking Changes

●Issue #1

The legacy ACL system deprecated in Consul 1.4.0 has been removed.

✓Solution

Verify that nothing is still using the legacy ACL system before upgrading. Consult the [Migrate Legacy ACL Tokens Learn Guide](https://learn.hashicorp.com/tutorials/consul/access-control-token-migration) for migration steps.

●Issue #2

`consul acl set-agent-token master` command has been replaced.

✓Solution

Use `consul acl set-agent-token recovery` instead.

Migration Steps

  1. 1
    Verify that nothing is still using the legacy ACL system before upgrading.
  2. 2
    Migrate from `consul acl set-agent-token master` to `consul acl set-agent-token recovery`.

Release Summary

This release introduces Admin Partitions (Enterprise only) and significant improvements to Connect TLS configuration and Vault provider support. It also removes the legacy ACL system, requiring users to migrate before upgrading.

Need More Details?

View the full release notes and all changes for Consul Connect ent-changelog-1.11.0.

View Full Changelog