Join us

ContentUpdates and recent posts about Pelagia..
Link
@kaptain shared a link, 5 months, 2 weeks ago
FAUN.dev()

Turning Kubernetes Last Access to Kubernetes Least Access Using KIEMPossible

KIEMPossible is a new open-source tool for Kubernetes entitlement cleanup. It maps out who has access to what - roles, entities, permissions - and shows how those are actually used across your clusters. Think of it as a permission microscope for AKS, EKS, GKE, and even the DIY K8s crowd. It breaks d.. read more  

Turning Kubernetes Last Access to Kubernetes Least Access Using KIEMPossible
Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

How I Built a 100% Offline “Second Brain” for Engineering Docs using Docker & Llama 3 (No OpenAI)

Senior Automation Engineer built an offline RAG system for technical documents using Ollama, Llama 3, and ChromaDB in a Dockerized microservices architecture. The system enables efficient retrieval and generation of information from PDFs with a streamlined UI. The deployment package, including compl.. read more  

Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

How to Evaluate LLMs Without Opening Your Wallet

A new mock-based framework lets QA and automation folks stress-test LLM outputs - no API calls, no surprise charges. It runs entirely local, usingpytest fixtures, structured test flows, and JSON schema checks to keep things tight. Test logic stays modular. Cross-validation’s baked in. And if you nee.. read more  

Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

I tested ChatGPT’s backend API using RENTGEN, and found more issues than expected

A closer look at OpenAI’s API uncovers some shaky ground: misconfiguredCORS headers, missingX-Frame-Options, noinput validation, and borkedHTTP status handling. Large uploads? Boom..crash!CORS preflightrequests? Straight-up denied. So much for smooth browser support... read more  

I tested ChatGPT’s backend API using RENTGEN, and found more issues than expected
Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

Cato CTRL™ Threat Research: HashJack - Novel Indirect Prompt Injection Against AI Browser Assistants

A new attack method -HashJack- shows how AI browsers can be tricked with nothing more than a URL fragment. It works like this: drop malicious instructions after the#in a link, and AI copilots likeComet,Copilot for Edge, andGemini for Chromemight swallow them whole. No need to hack the site. The LLM .. read more  

Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

AI and QE: Patterns and Anti-Patterns

The author shared insights on how AI can be leveraged as a QE and highlighted potential dangers to watch out for, drawing parallels with misuse of positive behaviors or characteristics taken out of context. The post outlined anti-patterns related to automating tasks, stimulating thinking, and tailor.. read more  

Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

Writing a good CLAUDE.md

Anthropic’s Claude Code now deprioritizes parts of the root context file it sees as irrelevant. It still reads the file every session, but won’t waste cycles on side quests. The message to devs: stop stuffing it with catch-all instructions. Instead, use modular context that unfolds as needed - think.. read more  

Writing a good CLAUDE.md
Link
@kala shared a link, 5 months, 2 weeks ago
FAUN.dev()

1,500+ PRs Later: Spotify’s Journey with Our Background Coding Agent

Spotify just gave its internal Fleet Management tooling a serious brain upgrade. They've wired inAI coding agentsthat now handle source-to-source transformations across repos - automatically. So far? Over 1,500 AI-generated PRs pushed. Not just lint fixes - these include heavy-duty migrations. They'.. read more  

1,500+ PRs Later: Spotify’s Journey with Our Background Coding Agent
Link
@devopslinks shared a link, 5 months, 2 weeks ago
FAUN.dev()

How when AWS was down, we were not

During the AWS us-east-1 meltdown - when DynamoDB, IAM, and other key services went dark - Authress kept the lights on. Their trick? A ruthless edge-first, multi-region setup built for failure. They didn’t hope DNS would save them. They wired in automated failover, rolled their own health checks, an.. read more  

How when AWS was down, we were not
Link
@devopslinks shared a link, 5 months, 2 weeks ago
FAUN.dev()

Collaborating with Terraform: How Teams Can Work Together Without Breaking Things

When working with Terraform in a team environment, common issues may arise such as state locking, version mismatches, untracked local applies, and lack of transparency. Atlantis is an open-source tool that can help streamline collaboration by automatically running Terraform commands based on GitHub .. read more  

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.