Nikolas Gehrmann

Cloud engineering beyond the architecture diagram.

Field notes, architecture records and investigations from working with Azure, Kubernetes, Terraform, networking and cloud security.

Architecture diagrams describe the intended system.

These notes are mostly about what happens afterwards.

Professional profile ↗
01

Operational Friction

The interesting parts of cloud engineering usually begin where the architecture diagram ends.

Network

Name resolution does not prove reachability.

Private connectivity depends on DNS, routing, network policy and the actual workload path.

DNS / ROUTING / PRIVATE ENDPOINTS

Operations

Availability controls can prevent maintenance.

Disruption budgets, replica placement and workload state determine whether infrastructure can move safely.

PDB / DRAIN / WORKLOAD STATE

Platform

Repository structure becomes part of the control plane.

GitOps remains manageable only when ownership, environments and deployment boundaries stay explicit.

GITOPS / OWNERSHIP / ENVIRONMENTS

02

Architecture Records

No architecture records published yet.

03

Lab

No lab entries published yet.