Production infrastructure / disciplined operations
IT Infrastructure Engineer for Linux, OpenShift, automation, and production-safe change.
I focus on infrastructure work that starts with observed symptoms, builds a defensible hypothesis, and limits change until validation and rollback criteria are clear.
Resume PDF is not published on this site yet. Use the contact page for the latest resume.
ok 01
Linux host and service investigation
ok 02
OpenShift and Kubernetes operational troubleshooting
ok 03
Incident triage, evidence capture, and escalation handoff
ok 04
Automation with validation and rollback paths
ok 05
KVM/libvirt lab design for repeatable testing
ok 06
Change planning, operational risk notes, and post-change review
Operating posture
01
Establish scope and baseline signals before touching production systems.
02
Automate checks and repeatable tasks without hiding failure modes or risk.
03
Define rollback triggers, validation evidence, and communication paths before change.
Case studies
A sanitized example of tracing intermittent outbound connectivity through workload, node, cluster policy, and perimeter control points before recommending a narrow change.
A sanitized investigation of Linux latency symptoms where disk I/O, memory reclaim, and service behavior had to be separated before any host-level change was made.
A contained defensive research project for observing noisy SSH behavior while preserving isolation, log hygiene, and clear teardown controls.
Projects
Active lab pattern
A local virtualization lab that models production habits: reproducible builds, explicit readiness checks, read-only validation where possible, and documented rollback paths.
Sanitized research
A defensive research project for observing noisy SSH behavior in a contained environment with clear trust boundaries, sanitized logs, and no path to internal systems.