When the tunnel is up but traffic is dead
A WireGuard handshake proves that peers can exchange encrypted control traffic. It does not prove that application packets have a working path.
Aland Azad — DevSecOps Engineer, Kurdistan Region, Iraq
I build Kubernetes platforms, write the Helm charts and pipelines teams ship with, and turn what I learn into rules that people, and coding agents, can follow.
Simple first. Secure by default. Verified, not assumed.
Layer I · The work
Most of my work is the layer under someone else’s work. When I do it well, nobody thinks about it.
Clusters I can rebuild, not repair
Talos for the operating system, Pulumi for provisioning, kind for the lab. Cilium, Traefik, cert-manager, Kyverno and CloudNativePG on top. Every layer is declared in code, so a broken cluster is a rebuild, not an archaeology project.
Make the common path safe and boring.
Talos · Pulumi · Cilium · Traefik
Read the case studyFive charts, one way to ship
I maintain a small set of Helm charts: workload, job, edge and mariadb, all on one shared library. Reusable GitHub workflows test, package, push and sign them. Flux reconciles everything from three repositories: central, infrastructure and applications.
Change goes through Git. Controllers do the rest.
Helm 4 · Flux · GitHub Actions
Read the field notePinned, signed, or it doesn’t run
Images pinned by tag and digest, scanned with Trivy, signed keylessly with Cosign through GitHub’s OIDC token, and verified by Kyverno before a pod starts. Containers run as UID 10001 on a read-only filesystem with every capability dropped.
Turning safety off takes an explicit setting. Turning it on never does.
Cosign · Trivy · Kyverno · SBOM
Read the field noteRules for people and agents
My engineering standards live in one repository: 34 skills, every rule with a code like K8S-006. Coding agents load them before they touch a project and cite the code when they break a rule. They write; I review, commit, push and deploy.
If I correct the same mistake twice, it becomes a rule or a check.
AGENTS.md · Agent Skills · Claude Code
See the rules I keepLayer II · Borehole log
From source code to the packet leaving the edge. Failures don’t respect team boundaries, so I try not to either.
Field rule DNS before deployment YAML. Routes before controllers. Certificates before annotations.
| Depth | Layer | Toolkit | Approach |
|---|---|---|---|
| Application | TypeScript on Bun · Python with uv · Go · .NET · Rust · Java | Build | |
| Delivery | GitHub Actions · Flux · Helm 4 · Kustomize · GitLab CI | Ship | |
| Security | Cosign · Trivy · Grype · Kyverno · Sealed Secrets · OpenBao · PKI | Harden | |
| Platform | Kubernetes · Talos · Cilium · Traefik v3 · cert-manager · CloudNativePG | Operate | |
| Infrastructure | Pulumi · OpenTofu · Cloudflare · AWS · Linux · mise | Provision | |
| Network | DNS · TLS · WireGuard · NetBird · nftables · routing · NAT | Trace |
Layer III · Principle
When something behaves strangely, fix it. Don’t document the surprise.
It’s rule six of eight I keep. The interesting work sits at the seams: a deploy that turns out to be a DNS problem, a security control that turns out to be a developer-experience problem. I follow it down until the cause has a name, then fix that. All eight rules
Layer IV · Field notes
Each note starts with a symptom and ends at the cause, usually one layer lower than it first looked.
All 6 field notesA WireGuard handshake proves that peers can exchange encrypted control traffic. It does not prove that application packets have a working path.
PKI becomes easier to reason about when it is treated as trust-chain and lifecycle design, not as a sequence of certificate-generation commands.
GitOps is most useful when desired state, reconciliation order, and ownership boundaries are explicit enough to operate under failure.
Ingress failures become tractable when DNS, TLS, edge reachability, controller routing, service discovery, and workload health are tested as one path.
Reusable CI should standardize security and delivery behavior across languages while leaving language-specific build logic explicit.
Restoring etcd data is one step in Kubernetes recovery; control-plane identity, manifests, endpoints, certificates, and reconciliation still have to agree.
Layer V · Path
Software engineering first. Then automation, where I learned that most slow processes are systems with people inside them. Now platforms, where both meet.
Read it like any section through rock: the newest layer sits on top.
More about me2026 → now
Kurdistan Region Government · DIT
Platform engineering, GitOps, CI/CD, Kubernetes operations and security. Most of the job is making the safe path the easy one, then writing it down so the next team doesn’t solve the same problem again.
Current layer2025 → 2026
Asiacell Communications
Automation across technology, finance, procurement, cybersecurity and operations. It taught me to connect technical decisions with the people, processes and controls around them, and that a fix nobody adopts isn’t a fix.
2024
American University of Iraq, Sulaimani
The bedrock: software engineering, networking, distributed systems, computing platforms and design patterns. Where I learned to read the layer below the one that’s failing.
Tap one for the specimen sheet: what it tests, how it’s weighted, and where it shows up in my work.
Specimen 01 · Certification
A vendor-neutral certification from the Linux Foundation and the CNCF that verifies the skills to perform the duties of a Kubernetes administrator. It is performance-based: every task is solved live on a command line running Kubernetes, not picked from multiple choice.
Exam domains, by weight
The same ground as my platform work: cluster lifecycle, networking, and troubleshooting from the node up.
Specimen 02 · Certification
Validates the ability to design solutions on AWS based on the AWS Well-Architected Framework: architectures that are secure, resilient, high-performing, and cost-optimized, and the judgement to review existing solutions for improvements.
Exam domains, by weight
AWS sits in the infrastructure layer of my toolkit, next to Pulumi, Linux, and Cloudflare.
Specimen 03 · Degree
A Bachelor of Science in Software Engineering from the American University of Iraq, Sulaimani.
What it laid down
The foundation the rest of the stack is built on.