Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Containers, Kubernetes, Docker and related technologies.

Inference Optimization Techniques. Ray vs. vLLM vs. KubeRay

Serving large language models at scale is fundamentally a distributed systems problem. A single GPU, or even a single node, is rarely enough once you need multiple models, multiple replicas, tensor-parallel sharding across GPUs, or high-availability rollouts. Kubernetes solves general container orchestration well, but it has no native concept of a GPU-aware, actor-based compute cluster.

GPU Cloud security: Isolation, multi-tenancy, and protecting sensitive training data

GPU cloud security tends to get discussed as if it's the same problem as general cloud security. It isn't. GPUs sit between processes in ways CPUs don't. Training data passes through them in patterns that create specific exposure. Model weights derived from sensitive data are themselves sensitive material in ways most procurement processes don't recognize. And the multi-tenant nature of public GPU cloud creates failure modes that don't exist in CPU-only environments.

Kernel-Level Visibility Without Instrumentation: What eBPF Changes for Container Security

Containers have changed how applications are built and deployed, but they have also made security visibility more difficult. Workloads are short-lived, services communicate constantly, and application behavior is distributed across containers, nodes, APIs, processes, and open-source dependencies. This is why many security teams are pairing eBPF with application-level runtime security. eBPF observes activity from the Linux kernel without requiring teams to modify every application, while runtime application security explains which code caused that activity.

GPU Cloud for non-AI workloads: Rendering, simulation, and scientific computing

The GPU cloud conversation over the last three years has been almost entirely captured by AI. Marketing pages talk about training, inference, and foundation models. Vendor announcements focus on which NVIDIA card fits which LLM. Reference customers are AI companies. The infrastructure decisions being made in the market are shaped by AI's specific requirements - high VRAM, fast interconnect, FP8 support, continuous utilization patterns.

The New MCP Headers Are a Gift to Gateways

In short, buried in the transport section of the MCP 2026-07-28 release candidate are three changes that matter more to infrastructure teams than to anyone else: mandatory Mcp-Method and Mcp-Name headers, cache-control-style ttlMs and cacheScope fields, and standardized W3C Trace Context propagation. Together with the stateless core, they turn MCP from a protocol that gateways had to fight into one that meets them halfway.

Kubernetes GPU Scheduling for MLOps and GPU Sharing

The default Kubernetes scheduler was built for stateless services: web servers, APIs, databases. It schedules a pod, checks that a node has enough of whatever resources were requested, and binds it. For CPU and memory, that model works fine. For GPUs, it falls apart in three specific ways. First, GPUs are treated as an opaque integer resource.

If they can turn it off, you don't own it - The AI kill switch problem

If someone else can turn it off, you don't own it. And most organisations haven't fully reckoned with what that means for their AI strategy. Civo Product Director Russ Smith draws a direct line from the Broadcom/VMware licensing shock to the Anthropic model restrictions, two different industries, same structural problem. When a vendor can change the rules overnight, businesses that built their strategy around that vendor are left with uncertainty and no clear next step.

NVIDIA B300 vs. NVIDIA B200: Blackwell Ultra vs. Blackwell

The Blackwell architecture arrived in 2024 as NVIDIA's answer to the next era of AI compute. The B200 set a new standard for inference performance, memory capacity, and training throughput, and many teams are still ramping up their use of it today. Then came Blackwell Ultra. The B300 is built on the same silicon foundation as the B200: same dual-reticle die design, same TSMC 4NP process node, same NVLink 5 interconnect.

VM Migration - What Happens to Your NSX Segments in Kubernetes?

Planning a migration off NSX usually starts with a networking conversation. Segments, VLANs, routing topology and BGP peering are not things that map cleanly to Kubernetes-native constructs the way the NSX distributed firewall maps to Calico’s tiered microsegmentation. NSX virtualizes the network layer in ways that Kubernetes doesn’t replicate by default. There is no native concept of a Layer 2 segment or VLAN, for instance.

Managing slow container starts with Kubernetes readiness probes

Imagine if your workday started as soon as you woke up. Before you can even start your coffee maker, email alerts are flooding in, coworkers are pinging you on Slack, and your phone is buzzing nonstop with reminders. You haven’t even pulled the covers back, and your boss is asking you about deliverables. This is what Kubernetes pods deal with every day. Unless, that is, you use readiness probes.