I am Trinidad Marroquin, an SRE / DevOps engineer focused on reliable infrastructure, practical automation, and systems that can be understood under pressure.
I work across the parts of the stack where infrastructure provisioning, Kubernetes platforms, deployment pipelines, observability, and production operations meet. My day-to-day interests include Kubernetes, Terraform, Rancher, Packer, CI/CD, Linux systems, metrics, logs, alerting, and the documentation needed to keep systems maintainable over time.
I value systems that are simple enough to debug during an incident. That usually means clear ownership, reproducible builds, versioned infrastructure, useful alerts, tested recovery paths, and runbooks that describe how the system actually behaves.
Engineering Approach
- Prefer explicit configuration and documented tradeoffs over clever abstractions.
- Automate repetitive work while keeping the automation easy to inspect and recover.
- Treat reliability as the result of design, operations, feedback loops, and team habits.
- Build dashboards and alerts around decisions operators need to make.
- Reduce production surprise through small changes, clear rollbacks, and repeatable recovery.
Areas I Work In
- Kubernetes cluster operations, platform reliability, and Rancher-based management.
- Infrastructure provisioning and change review with Terraform.
- Machine and image build workflows with Packer.
- CI/CD pipelines that separate validation, promotion, and deployment.
- Observability with metrics, logs, dashboards, alerts, and incident follow-up.
- Linux systems, scripting, troubleshooting, and production support.
How I Think About Systems
Good infrastructure should be boring for the right reasons. It should be repeatable, observable, documented, and recoverable. When something fails, the system should provide enough signal for an operator to form a useful hypothesis quickly.
I prefer operational maturity that shows up in everyday work: readable repositories, consistent naming, reviewable plans, clear pipeline output, alerts tied to action, and documentation that reflects how the system is actually run.
This site is where I collect project notes, operational lessons, and technical writing that may be useful to other engineers working on similar systems.