Skip to content
OctaFuse OctaFuse

OctaFuse 2.2.0: routing policy for every priority tier

Published

Later change: migration 0021 in v2.3.0 renamed cache_affinity / fixed_order to hash_affinity / weight_priority with no compatibility aliases. The text below preserves the 2.2.0 release context; use the v2.3.0 release notes for current configuration.

OctaFuse Gateway 2.2.0 is now available. This release makes routing configuration more closely reflect real production traffic.

Highlights

Section titled “Highlights”
  • One Gemini routing semantic: public Surfaces and upstream Targets now use models.generate. Streaming and non-streaming requests share one Route Pool while the actual wire action remains visible in route_trace.gemini.action.
  • Per-tier routing strategies: each priority tier in a Route Pool can override its ordering strategy, while unconfigured tiers continue to inherit the Pool, model, or global strategy.
  • Canonical strategy IDs: cache_affinity, weighted_random, fixed_order, and weighted_round_robin now form one contract across Admin, API, storage, and runtime.
  • Clearer Admin controls: visual strategy selectors expose the effective policy source and Failover rules for each tier.
  • Agent Tools Provider cards: credentials, activation, and Standard / Charged / Metered pricing now live in one focused workflow.

Upgrade notice

Section titled “Upgrade notice”
  • If all existing routing policies inherit the global configuration, you can upgrade to 2.2.0 without interruption.
  • If models, Pools, or priority tiers have their own policy configuration, requests may briefly fail while old and new data are inconsistent. Apply the database migrations and upgrade Proxy and Admin within the same maintenance window.

Get 2.2.0

Section titled “Get 2.2.0”

Learn more about OctaFuse or explore the source:

If OctaFuse is useful to your project, consider giving the repository a Star. Your interest and feedback help us keep improving multi-Provider routing.