TLDR DevOps 2026-10-28
Agent-Scale Git ⚖️, vLLM Accuracy 🎯, PyTorch 2026 🔥
Together With
Add RAG to your Elastic stack (Sponsor)
Your data is already in Elasticsearch — use
Elastic Cloud to power Retrieval Augmented Generation (RAG). Skip the new database and add vector storage and LLM-powered search without changing your stack.
- Reuse your data layer: Store vector embeddings directly in Elasticsearch indices alongside your existing data — no separate vector database required
- Wire up RAG end to end: Connect Elastic Cloud, LangChain, and Amazon Bedrock with a working Python pipeline from document ingestion to LLM query
- Access models through a unified API: Use Elasticsearch's Open Inference API to call Amazon Bedrock models for chat completion and text embeddings
Follow the step-by-step tutorial and start asking questions of your data today.
Build a RAG pipeline on AWS >
How to Build Golden Paths in Platform Engineering (19 minute read)
Spacelift defines a golden path as an opinionated, documented, self-service route for a common task. The guide lists five building blocks and four rollout phases, with a worked Postgres example on AWS built as an rds-postgres module using OpenTofu 1.10.3. Production gets Multi-AZ and deletion protection.
Why Kubernetes autoscalers keep fighting each other (and why the solution must be autonomous) (7 minute read)
Nikhil Kurup argues that HPA, VPA, KEDA, and Karpenter mutate the same workload fields from independent loops, producing four failure modes, including a VPA and HPA death spiral and GitOps drift ping-pong. He calls for a unified, predictive autoscaler with explainable decisions.
The Bridge to Agent-Scale Git Infrastructure (8 minute read)
GitHub is replacing repository-wide write serialization with per-reference quorums to overcome cross-region latency during its Azure migration. Internal tests showed 3–4x higher throughput for writes to different references, while an object-storage-backed design allows read capacity to scale independently.
How do you respond when your AI tooling and models fail? (Sponsor)
Engineers from
incident.io and Skyscanner discuss what happens when AI tooling becomes a single point of failure, and what both teams are doing about it.
Watch Now→Agent-Reach (GitHub Repo)
Agent-Reach is an open source CLI tool that lets agents read and search platforms like Twitter, Reddit, YouTube, GitHub, and Bilibili without API fees. It handles login-gated sites, video content, and Chinese platforms to provide structured data for AI agents.
OpenBot (GitHub Repo)
OpenBot is a local-first desktop workspace for persistent AI teammates that runs Codex, Claude, Grok, and Gemini with dedicated workspaces and task queues. It provides a shared desktop channel, file transfers, and an embedded browser that agents can control. A development preview is available for macOS, Windows, and Linux.
Fixing Tool-Call Accuracy in vLLM (7 minute read)
vLLM 0.31 can achieve 100% tool-call schema accuracy for Kimi and DeepSeek models through constrained decoding, a technique that guarantees schema adherence during token generation. This fixes a reliability issue where vLLM 0.28 produced invalid tool calls 8% of the time, causing agentic workloads to build up nonsensical context.
Before you expand your GPU pool, measure the outcome (8 minute read)
Teams should define each workload's outcome and deadline before expanding a GPU pool. Teams can stagger flexible jobs, load test sustainable serving capacity, and track cost per verified outcome with OpenCost before adding GPUs.
Get our free daily newsletter with curated tools 💻, trends 📈, and insights 💡, for DevOps Engineers 👨💻
Join 350,000 readers for
one daily email