Removed v1 HTTP is the Important line in Jaeger 2.21.0

So Jaeger Releases put v2.21.0 on the feed, dated September 14, 2026. We flagged it Important as a breaking change. The release note is kind of a wall. Backend Changes opens with a Breaking Changes block, then New Features, then a long bug-fix list. Recency wants the cheerful bits: ClickHouse storage promoted to stable, MCP search that can omit the service name. Fine. Those are the names people screenshot.

The line that matters, to the best of my understanding, is the first Breaking Changes bullet: Feat(query)!: remove v1 http endpoints the ui no longer calls. Your AE forwards 2.21.0. A customer still hitting the old v1 HTTP query surface starts failing overnight. Same block replaces ai.enable_mcp with an optional ai.mcp config block, and Elasticsearch now rejects five unsupported config keys at startup. Real partner-ticket material. ClickHouse stable is worth a sentence if you sell storage backends. It is not the break.

I keep almost filing Jaeger under "observability bump, ignore." Kind of the wrong habit when you sell next to tracing stacks or anyone whose dashboards still call the old query HTTP paths. The New Features section will pull eyes toward MCP tooling. That is fine for a roadmap slide. It is kind of useless when the renewal question is why search stopped answering on the old URL.

Tracking product change here means reading past the emoji headers and asking which line changes a partner ticket. Let's say the talking point is not "2.21 shipped ClickHouse stable." It is the v1 HTTP endpoints are gone, then check whether your ai.enable_mcp config needs the new ai.mcp shape, then yes mention ClickHouse if the prospect cares about storage. We pull it into a uniform entry shape at /sources/jaeger-releases. Same JSON as everything else. Recency still wants stable and MCP. Recency is not the removed endpoints.