Cuong Nguyen
Cloud Solution Engineer
Hanoi, Vietnam
Actions
Cloud and Infrastructure Engineer with 6 years of experience in DevOps and distributed storage systems for Telco Cloud environments — from architecture design to day-2 operations and troubleshooting. Recently focused on integrating AI agents into Kubernetes observability to reduce manual toil in incident response, with a passion for sharing production-tested, reusable patterns with the open infrastructure community.
Badges
Area of Expertise
Topics
Investigate First, Decide Second: The Missing Step in Kubernetes Alert Response
"We automated the investigation, not the fix."
Every DevOps engineer knows the drill. Alert fires. Open AlertManager, switch to Kibana, check Grafana. Correlate manually across three tools. At 2AM, this takes a hour before you know enough to act.
On Kubernetes 1.33, we integrated an AI agent that reads alerts from AlertManager, queries logs from Elasticsearch, pulls metrics from Prometheus assembling a structured investigation before anyone is paged. The engineer receives a brief, not a fire alarm.
Three scenarios, same stack, different outcomes:
- CrashLoopBackOff: agent identifies OOMKill pattern across 3 restart cycles — engineer approves fix in 5 minutes, not 1 hour
- ImagePullBackOff: Kibana is empty because container never started
- OOMKilled: Prometheus memory trend reveals misconfigured resource limit — fix proposed before engineer opens a single tab
Attendees leave with a reusable investigation pipeline and approval gate design for AI-assisted alert response on Kubernetes.
Changing the Engine Mid-Flight: Zero-Downtime Ceph Upgrades
"Upgrade Ceph in our telco cloud with zero downtime." That is a mandatory requirement every 1–2 years to ensure security patches, bug fixes, and continued support from vendors and the community. We have a Ceph Cluster version with 10–50 nodes deployed on bare-metal running 5G Core workloads (AMF, UPF,...).
This talk covers a first-hand upgrade with three real failure scenarios:
- Monitor quorum loss: root cause analysis, recovery sequence, and how to prevent quorum degradation during daemon rolling restarts
- OSD storms triggered by rebalancing that threatened cluster stability
- Incompatible client versions silently blocking the upgrade path
Beyond failure recovery, we'll share the upgrade sequencing strategy we developed — covering pre-flight checks, daemon upgrade ordering (MGR → MON → OSD → MDS/RGW).
Attendees leave with a reusable pre-upgrade checklist and sequencing framework for bare-metal Ceph in high-stakes environments.
KubeCon + CloudNativeCon Japan 2026 Sessionize Event
KCD & OpenInfra Days Vietnam 2026 Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top