Platform Engineering · Cloud · Kubernetes · GitOps · Infrastructure as Code · DevOps/SRE
I build evidence-backed infrastructure and platform projects around Kubernetes, GitOps, Terraform, Azure, developer experience, and operational automation. The work is designed to be reproducible: each repository records its architecture, trade-offs, validation method, and the boundary between implemented design and runtime evidence.
Platform Engineering · Kubernetes & GitOps · Cloud & Azure · Infrastructure as Code · CI/CD & Automation · Observability & SRE · DevSecOps
| Project | Engineering case |
|---|---|
| 01 · Cloud-Native Internal Developer Platform | Problem: connect developer self-service to governed, observable delivery. Stack: Backstage · Kubernetes · Argo CD · OpenTelemetry · Grafana · Kyverno · Vault. Proof: validation model and indexed evidence. |
| 02 · Azure Data Landing Zone Platform | Problem: establish a governed Azure foundation with secure state and controlled lifecycle operations. Stack: Terraform · Azure Policy · Azure networking · Microsoft Entra ID · GitHub Actions/OIDC. Proof: deploy–drift-check–destroy lifecycle record and test matrix. |
| 03 · DevOps Automation Toolkit | Problem: turn platform and cloud evidence into safe, deterministic operational reports. Stack: Python · Kubernetes · Terraform/OpenTofu · SARIF · JSON Schema · Bash/PowerShell. Proof: 20-tool traceability matrix and v1.0.1 release. |
| 04 · FluxVirt Lab | Problem: reconcile virtual machines and containers through one GitOps control plane. Stack: K3s · Flux CD · KubeVirt · CDI · Kustomize · Trivy. Proof: dated reconciliation record, v0.1.0 release, and bounded recovery record. |
| 05 · Flask Kubernetes GitOps Lab | Problem: separate artifact production from cluster reconciliation in a hardened delivery path. Stack: Flask · GitLab CI · Buildah · Kubernetes · Kustomize · Argo CD · Traefik. Proof: Minikube and Argo CD E2E record and validation report. |
Evidence-backed, machine-validated knowledge base covering 1,400+ DevOps, Cloud, Platform Engineering, SRE, and DevSecOps tools. Canonical YAML, schemas, generated documentation, and automated checks preserve lifecycle, licence, provenance, and review metadata for reproducible catalogue maintenance.
Design the platform → Govern the cloud foundation → Automate operations
→ Explore infrastructure boundaries → Deliver workloads safely
Evidence boundary: These are scoped engineering projects, not claims of production adoption. Their documentation distinguishes implemented design, static validation, retained lab or runtime evidence, and paths that were not exercised against live target environments.
Generated weekly from the public GitHub contribution graph. It does not create, backdate, or modify contribution history.