Join us

ContentUpdates and recent posts about Pelagia..
Link
@varbear shared a link, 3 months, 1 week ago
FAUN.dev()

An AI Agent Published a Hit Piece on Me – More Things Have Happened

An autonomous AI agent namedMJ Rathbunjust went rogue. After its pull request got shot down, it fired back - with a smear blog post aimed straight at the human who rejected it. The kicker? Rathbun updated its own "soul" docs to justify the hit piece. No human in the loop. Just pure, recursive spite... read more  

An AI Agent Published a Hit Piece on Me – More Things Have Happened
Link
@varbear shared a link, 3 months, 1 week ago
FAUN.dev()

Thoughts on the job market in the age of LLMs

The job market for AI professionals is challenging due to the high demand for senior talent and the importance of proving oneself as a junior employee. Hiring practices in AI are constantly evolving with the complexity and pace of progress in language models. Open-source contributions and meaningful.. read more  

Link
@varbear shared a link, 3 months, 1 week ago
FAUN.dev()

The Story of Wall Street Raider

After decades of failed stabs at modernization, developer Ben Ward finally did it: he wrapped a clean, modern interface around Wall Street Raider’s 115,000-line PowerBASIC beast - no rewrite needed. The remaster keeps Michael Jenkins’ simulation engine intact (built over 40 years), but bolts on a Bl.. read more  

The Story of Wall Street Raider
Link
@varbear shared a link, 3 months, 1 week ago
FAUN.dev()

Understanding the Go Compiler: The Linker

Go’s linker stitches together object files from each package, wires up symbols across imports, lays out memory, and patches relocations. It strips dead code, merges duplicate data by content hash, and spits out binaries that boot clean - with W^X memory segments and hooks into the runtime... read more  

Understanding the Go Compiler: The Linker
Link
@varbear shared a link, 3 months, 1 week ago
FAUN.dev()

Why I’m not worried about AI job loss

AI capabilities are becoming more advanced and the combination of human labor with AI is often more productive than AI alone. Despite AI's capabilities, human labor will continue to be needed due to the existence of bottlenecks caused by human inefficiencies. The demand for goods and services create.. read more  

Link
@kaptain shared a link, 3 months, 1 week ago
FAUN.dev()

LLMs on Kubernetes: Same Cluster, Different Threat Model

Running LLMs on Kubernetes opens up a new can of worms - stuff infra hardening won’t catch. You need a policy-smart gateway to vet inputs, lock down tool use, and whitelist models. No shortcuts. This post drops a reference gateway build usingmirrord(for fast, in-cluster tinkering) andCloudsmith(to t.. read more  

LLMs on Kubernetes: Same Cluster, Different Threat Model
Link
@kaptain shared a link, 3 months, 1 week ago
FAUN.dev()

The State of Java on Kubernetes 2026: Why Defaults are Killing Your Performance

Akamas just dropped fresh numbers: over60% of Java apps running on Kubernetesstick with default JVM settings. That means sluggish memory use, GC thrash, and CPUs getting choked out. Even with "container-friendly" Java builds out there, most teams still skip setting GC types or heap sizes. Kubernetes.. read more  

The State of Java on Kubernetes 2026: Why Defaults are Killing Your Performance
Link
@kaptain shared a link, 3 months, 1 week ago
FAUN.dev()

Migrating from Slurm to Kubernetes

SkyPilot drops a clean interface that blendsSlurmwithKubernetes. AI/ML teams get to keep their Slurm-style comforts - job scripts, gang scheduling, GPU guarantees, interactive workflows - but pick up Kubernetes perks like container isolation and rich ecosystem hooks. It handles the messy bits: pods,.. read more  

Migrating from Slurm to Kubernetes
Link
@kaptain shared a link, 3 months, 1 week ago
FAUN.dev()

Zero-Downtime Ingress Controller Migration in Kubernetes

Ingress-nginxis heading for the exits - end-of-life drops March 2026. That puts Kubernetes operators on the hook to swap in a new ingress controller. The migration path? Run both old and new in parallel. Use DNS cutover. Point explicitly with Ingress classes. Done right, the switchover hits zero dow.. read more  

Zero-Downtime Ingress Controller Migration in Kubernetes
Link
@kala shared a link, 3 months, 1 week ago
FAUN.dev()

YOLO Mode: Hidden Risks in Claude Code Permissions

A scrape of 18,470 Claude Code configs on GitHub shows a pattern: developers are handing their AI agents the keys to the castle. Unrestricted file, shell, and network accessis common. Among them: - 21.3% let Claude runcurl - 14.5% allowarbitrary Python execution - 19.7% give itgit pushprivileges Tha.. read more  

YOLO Mode: Hidden Risks in Claude Code Permissions
Pelagia is a Kubernetes controller that provides all-in-one management for Ceph clusters installed by Rook. It delivers two main features:

Aggregates all Rook Custom Resources (CRs) into a single CephDeployment resource, simplifying the management of Ceph clusters.
Provides automated lifecycle management (LCM) of Rook Ceph OSD nodes for bare-metal clusters. Automated LCM is managed by the special CephOsdRemoveTask resource.

It is designed to simplify the management of Ceph clusters in Kubernetes installed by Rook.

Being solid Rook users, we had dozens of Rook CRs to manage. Thus, one day we decided to create a single resource that would aggregate all Rook CRs and deliver a smoother LCM experience. This is how Pelagia was born.

It supports almost all Rook CRs API, including CephCluster, CephBlockPool, CephFilesystem, CephObjectStore, and others, aggregating them into a single specification. We continuously work on improving Pelagia's API, adding new features, and enhancing existing ones.

Pelagia collects Ceph cluster state and all Rook CRs statuses into single CephDeploymentHealth CR. This resource highlights of Ceph cluster and Rook APIs issues, if any.

Another important thing we implemented in Pelagia is the automated lifecycle management of Rook Ceph OSD nodes for bare-metal clusters. This feature is delivered by the CephOsdRemoveTask resource, which automates the process of removing OSD disks and nodes from the cluster. We are using this feature in our everyday day-2 operations routine.