Hao Ngo
Platform and DevOps engineer based in Hanoi, Vietnam. I build the delivery infrastructure that other engineers use every day.
The short version
I work on the layer between "the code is merged" and "the service is healthy in production". In practice that means Kubernetes clusters, Argo CD, Helm charts, Jenkins and GitLab pipelines, Terraform, and a steady effort to make all of it boring enough that nobody has to think about it.
My preference is for systems that explain themselves. A new engineer should be able to read a repository and understand how a change reaches production, without a meeting. Most of my best work has been deleting a special case rather than adding a clever one.
What I am good at
- Kubernetes operations — cluster lifecycle, workload design, RBAC, ingress and TLS, autoscaling, capacity and cost.
- GitOps delivery — Argo CD control planes, app-of-apps, environment promotion, sync waves and windows.
- CI/CD engineering — shared Jenkins libraries, GitLab CI templates, build and scan and sign, artifact registries.
- Infrastructure as code — Terraform modules and state discipline, Ansible for the things below the cluster.
- Observability — Prometheus, Grafana, Loki; alerts tied to symptoms rather than to metrics that merely look interesting.
Experience
Platform / DevOps Engineer
- Designed and operate an Argo CD control plane serving clusters in several regions.
- Standardised regional repositories around one directory contract, removing forked manifests.
- Built and version the shared pipeline library used for build, scan and GitOps commit.
DevOps Engineer
- Migrated services from VM deployments onto Kubernetes with Helm packaging.
- Rolled out a common monitoring baseline and trimmed the alert set to what gets acted on.
- Introduced image scanning and base-image refresh policy into the pipeline.
System & Automation Engineer
- Ran Linux fleets, web and database tiers, backup and restore drills.
- Replaced manual deploy runbooks with Ansible and the first CI pipelines.
Outside work
I read more infrastructure post-mortems than is strictly healthy, keep a homelab that exists mainly so I can break things safely, and write the notes on this site so that future me stops solving the same problem twice.
Get in touch
The fastest route is email: hello@haongo.dev. I am happy to talk about platform design, GitOps layouts, or a pipeline that has outgrown its YAML.