The knowledge to answer 'which services are exposed to the internet, and who owns them?' already exists — it's just scattered across a half-dozen tools that don't talk to each other. A knowledge graph is how you make it queryable.
A walkthrough of platform-kg: extract facts from ArgoCD, Kubernetes, Helm, GitHub, Terraform, Vault, and Istio, turn them into RDF triples, and load them into GraphDB — a graph of your actual cluster you can query in a browser.
Once you have a graph of your platform, the obvious question is: now what? It turns out there's a ladder of answers — inventory, ownership, dependencies, blast radius — each rung built on the one below, with real SPARQL at every step.
In 2026, the hard part of putting an AI agent on your infrastructure is no longer the AI — it's giving the agent something trustworthy to reason over. A platform knowledge graph is exactly that context layer, wired in over MCP.
The Horizontal Pod Autoscaler looks simple, but missing metrics, unset requests, averaging behavior, and stabilization windows can make it quietly do the wrong thing.
A practical tour of man page sections, local documentation paths, and command-line discovery techniques for learning Linux from the system itself.
How to connect traditional RPM packaging with GitHub Actions so packages can be built, archived, and distributed through a repeatable CI pipeline.
Using Bash's PS4 prompt with set -x to add timestamps, file names, line numbers, and useful context to shell trace output.
A deep look at Linux's built-in documentation culture, from the Unix Programmer's Manual to the man page system, and why learning how to use it changes how you learn Linux.
Creating a dedicated non-root Ansible user with sudo access and SSH key authentication for more secure Linux host management.