Shahzaib
Khan

ProblemServers were patched by hand on a monthly cadence, partly by an outside team, with after-hours manual swaps in production and real room for human error. Nothing healed itself.

I built the pipeline end to end. A scheduled trigger starts CI, which bakes a new machine image, versions the launch template, and rolls it out through a health-gated instance refresh.

A lifecycle hook and a per-application health check confirm each new instance is actually serving traffic before the old one retires, which is what makes the refresh safe rather than merely automatic.

The first phase runs on its own to a test environment and opens tracking tickets. The second phase waits for a human approval, then rolls canary style to the remaining environments including production, with notifications at every step.

ResultRemoved a standing external dependency and hours of after-hours on-call work every cycle. Monthly patching became a hands-off, reliable and auditable process across every environment.

ProblemKubernetes management was scattered across tools, production and non-production lived in different places, and there was no single view of the fleet or its cost. There was also no lightweight anomaly detection independent of the main monitoring stack.

I co-built a read-only platform that pulls several sources into one fleet view covering clusters, nodes, workloads, logs and manifests.

On top of that we added independent anomaly detection with trend analysis over stored time-series data, per-cluster and per-namespace cost visibility, and fast workload search.

An assistant answers questions grounded in the data the platform has already collected, rather than making live calls out to the clusters.

ResultOne place for engineers and leadership to see the whole fleet, its health and its cost. Live and in use.