Directus vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Directus is on a steady weekly cadence with AI tooling deepening on every release.
Directus is shipping weekly point releases on the 11.17.x line, each carrying a mix of small UI features, AI-related additions, and dependency hygiene. The recent stretch added a /ai/object structured-generation endpoint, an asset cache-revalidation header (ASSETS_CACHE_REVALIDATE), background data imports with timeout and concurrency controls, a Tabs group interface that absorbs a previously-extension feature, and comparison-modal improvements (timezone-aware datetime, modified-only view). UI work in 11.17.0 also shrunk the app to 90% and converted px to rem — flagged as a potential breaking change for extensions with hardcoded pixel values.
Two parallel arcs: (1) AI Assistant continues to grow — image/PDF upload, multi-provider model refresh (Anthropic, Google, OpenAI), an Anthropic tool-search adapter for context efficiency, and now a structured-object endpoint for inline experiences; (2) the app shell is being modernized — rem-based sizing, native replacements for previously third-party UI primitives (reka, native Tabs), and migration of @directus/visual-editing into the monorepo. Bug-fix volume is high but consistent — typical of a project absorbing a wide community contribution stream.
Expect continued weekly 11.17.x cuts focused on the AI surface (more inline AI-aware components, more structured-output use cases) and the in-progress monorepo consolidation. The 90%-UI shrink will likely require an extensions-side migration cycle before a major version cut.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to Directus →
See more alternatives to Kubernetes →