/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

  1. The Shift to cgroup v2 in Kubernetes: What You Need to Know

    Kubernetes has deprecated cgroup v1 in favor of cgroup v2, with complete removal scheduled for future releases. The transition requires migrating Linux nodes, updating container runtimes, and verifying kernel compatibility. Adopting cgroup v2 enables advanced features such as Memory QoS, improved OOM handling, and pressure stall information metrics.

    DEPTH ■■■■■12 min read2 weeks ago

    Sign in to save and rate

  2. Scaling Kubernetes Workloads with Node Swap

    Kubernetes memory limits often cap node density for bursty agentic AI workloads that sit idle with large memory footprints. To solve this, the engineering team benchmarked Kubernetes v1.34 node swap backed by fast NVMe Local SSDs across CI/CD builds, headless browsers, and Python sandboxes. The approach successfully increased pod density up to three times without significant latency costs.

    DEPTH ■■■■■6 min read2 weeks ago

    Sign in to save and rate

  3. It's time to make your own RSS reader

    This post walks through the process of self-hosting a personal RSS reader using FreshRSS and Docker, secured privately over a Tailscale network. The author details the configuration of environment variables, auth keys, and Docker compose deployment to avoid exposing the service to the open web. The result is a private, algorithm-free news reader accessible across multiple devices and integrable with external reading apps or AI agents.

    DEPTH ■■■■■10 min read9 days ago

    Sign in to save and rate

  4. Why Is My Kubernetes Job Still Pending? Tracing Kueue Admission with Headlamp

    Kubernetes jobs managed by Kueue can remain pending while waiting for admission checks and resource allocation. The team implemented a Kueue plugin for Headlamp to trace pending workloads through local queues, cluster queues, and resource flavors within a unified interface. This approach allows engineers to quickly determine whether a job is blocked by admission policies or standard pod scheduling.

    DEPTH ■■■■■9 min read11 days ago

    Sign in to save and rate

  5. Your agent, your network: How Meta’s Muse agent works with Tailscale

    Meta integrated Tailscale into its Muse personal AI agent, allowing the agent to join a user's tailnet as a separate node and interact with self-hosted services and SSH sessions. By treating Muse like any standard tailnet node, users can apply Tailscale's access controls, grants, and tags to enforce security and adhere to the principle of least privilege.

    DEPTH ■■■■■5 min read3 weeks ago

    Sign in to save and rate

  6. Why I tried to kill token billing (and why we kept it)

    The author examines the limitations of token-based billing as a customer-facing pricing model, noting that it exposes internal margins and commoditizes AI products. The company explored abandoning token billing entirely but realized its necessity for backend cost tracking and margin management. Ultimately, the piece proposes unified credits and output-based pricing as better ways to align invoices with customer value.

    DEPTH ■■■■■7 min read3 weeks ago

    Sign in to save and rate