Weekly Update — June 1 – 8, 2026 #2210
missBerg
announced in
Weekly Updates
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
v0.7.0 shipped this week — multi-tenant hostname routing, two new provider translation paths (Anthropic → Bedrock Converse and Azure OpenAI Responses), OpenAI audio transcription/translation endpoints, and the first runtime step toward quota-aware rate limiting. Thanks to everyone who landed code, reviewed, and weighed in on the road to GA. 🎉
🛣️ Road to v1.0 GA — v0.7.0 is out
v0.7.0 shipped on June 6, the last feature release before the mid-June GA. Full notes are on the release page and the docs site. The headline items:
AIGatewayRoute.spec.hostnamesscopes a route (and its/v1/modelslisting) to specific hosts, soteamA.ai.example.comandteamB.ai.example.comeach see only their own model catalog through one Gateway. Wildcards follow Gateway API matching rules./v1/messages→ AWS Bedrock Converse — Anthropic-native clients can now reach any Bedrock model (text, images, tool use, thinking, streaming) without changing their integration. Azure OpenAI Responses API and OpenAI audio transcription/translation endpoints land in the same release.QuotaPolicyto anAIServiceBackendnow injects a backend rate limit filter for per-backend throttling. Full quota-aware routing across backends is the follow-on work.displayparameter and the newxhigheffort tier are supported for long-horizon agentic and coding tasks.Two breaking changes to flag before you upgrade:
AIGatewayRoute.spec.rulesis now capped at 15 (down from 128) to match the Gateway APIHTTPRoutelimit. Split larger routes across multipleAIGatewayRouteresources on the same Gateway.displaydefaults toomitted(earlier Claude models defaulted tosummarized). Setdisplay: "summarized"explicitly if you want thinking content back.Next on the GA track: the MCPBackend CRD and full quota-aware routing across multiple backends — see the proposals below.
✨ What's new
Everything that shipped this cycle is in v0.7.0 above —
mainhas only just reopened post-release, so there's no separate post-release work to list yet. Expect the usual run of merges in next week's update.💡 New design proposals & feature requests
A few new threads worth a read if any of these are in your wheelhouse:
input_audio_seconds/output_audio_secondsCEL variables so operators can price per minute.MCPRoute— flagged as next-up on the v0.7+ roadmap.👀 PRs looking for review
If you have time to help review, these are open and waiting:
max_requestsconfigurable via Helm by @PatilHrushikesh — lifts the hard-coded 1024 request cap so high-concurrency deployments can tune it.InferencePoolas a backend reference onAIServiceBackendby @isztldav — routes inference-pool backends through the sameAIServiceBackendsurface as other providers.🙏 Thanks to this week's contributors
@aabchoo, @hustxiayang, @yuzisun, @ajac-zero, @sivanantha321, @aishwaryaraimule21, @PatilHrushikesh, @arpitjain099, @anurags25, @nacx, @Killusions, @mtparet, @guohao, @sandangel, @kanurag94, @Hritik003, @albe2669, @isztldav, @ChrisJBurns, @immanuwell, @CodePrometheus, @xianml, @PraveenKumarInjam, @saixso, @missBerg — and everyone who showed up to triage, review, and discuss.
See you next week!
All reactions