New whitepaper: Your GPU Is Up. Is Your AI?
Introducing the Inference Resilience Profile, a public proposal for testing AI service continuity across Kubernetes and NVIDIA GPU failure domains.
Kubernetes
Binding AI Agent Approvals to Kubernetes Changes
Bind approval to the exact Kubernetes request, object identity, starting state, executor, and validity window. Use conditional patches while keeping authorization, approval consumption, and uncertain outcomes separately governed.
From Simulation to Kubernetes: Testing Agent Identity and Admission
Move from an offline simulation to a disposable Kubernetes cluster. Test separate agent, executor, and observer identities, resource-scoped permissions, admission rules, and independent state readback.
AI Agent Stability: When Retries Become the Incident
Prevent retries and corrective actions from amplifying an incident. Define retry ownership, finite budgets, stabilization rules, and reconciliation for actions whose outcomes remain unknown.
AI Agent Verification: Prove the Outcome, Not the Tool Call
Verify the outcome of an agent action beyond the tool response. Separate acceptance, configuration, convergence, and service evidence, then test the conditions that could produce a false success report.
Operating Kubernetes as a Platform Product: SLOs, Upgrade Gates, Capacity, and Recovery
Operate Kubernetes as a service application teams can depend on. Define workload profiles, service objectives, upgrade evidence, disruption capacity, and recovery criteria before expanding the platform.
Infrastructure Change Evidence: What to Capture Before, During, and After a Change Window
Capture the evidence needed to approve, execute, validate, and recover an infrastructure change. Preserve service outcomes, exceptions, decision ownership, and access-controlled records for the next engineer.
AI Inference Disaster Recovery: Designing Model Serving for Regional and Platform Failure
Design AI inference recovery around the complete approved service. Include models, retrieval, authorization, application state, capacity, interrupted requests, and tested degraded modes.
Hybrid Certificate Lifecycle Architecture: Trust Across VCF, NSX, Kubernetes, and Azure
Manage certificates as working trust relationships across VCF, NSX, Kubernetes, and Azure. Coordinate ownership and renewal while preserving supported local mechanisms and proving activation through service transactions.
Why Mirantis k0rdent AI Is the AI Factory Operating Layer the Market Has Been Missing
TL;DR The AI infrastructure market has spent too much time treating GPU acquisition, Kubernetes deployment, workload scheduling, model serving, and platform governance as separate purchases. Enterprises and neoclouds do not experience them separately. They experience the gaps between them, where driver mismatches, operator ordering, network configuration, tenant policy, lifecycle ownership, and support boundaries turn expensive … Explore: Why Mirantis k0rdent AI Is the AI Factory…
GPUs Are Not a Cloud: Why Neoclouds Need Vendor Neutral AI Infrastructure Orchestration
TL;DR Neoclouds may begin by selling access to scarce GPU capacity, but long-term differentiation requires more than racks, drivers, and a booking portal. A production AI cloud must convert bare-metal servers, virtual machines, GPU pools, storage, networks, and external cloud resources into secure, repeatable, tenant-aware services. The missing layer is vendor-neutral AI infrastructure orchestration. It … Explore: GPUs Are Not a Cloud: Why Neoclouds Need…
KB 439327: How to Find and Register Newer VKS Releases in vCenter
TL;DR A newer VMware Kubernetes Service version may be missing from the vCenter upgrade interface even when the environment is functioning correctly. VKS versions bundled with the installed vCenter build appear automatically. Newer asynchronous VKS releases must first be downloaded from the Broadcom Support Portal and registered by uploading the release’s package.yaml file. Registration does … Explore: KB 439327: How to Find and Register Newer…