Priya Namasivayam
EarnIn, Staff Platform Engineer
Dublin, California, United States
Actions
Priya Namasivayam is a Staff Platform Engineer at EarnIn, where she builds and operates cloud-native platform infrastructure at scale. She specializes in Kubernetes, service meshes, and GitOps-driven delivery, and led EarnIn's migration from AWS App Mesh to Linkerd—improving security, reliability, and developer experience.
She focuses on treating platform infrastructure like application code: modeling infrastructure tests as Kubernetes resources and gating Flux-driven changes with in-cluster validation using Testkube. Priya is passionate about simplifying complex systems and sharing practical patterns teams can adopt in production.
Area of Expertise
Topics
Shift-Left for Platform Teams: Kubernetes-Native Infrastructure Testing at EarnIn
EarnIn operates a high-availability fintech platform on 15+ CNCF projects, including Flux, Karpenter, Kyverno, cert-manager, Linkerd, external-secrets-operator, Argo CD, Velero, and more. When infrastructure components fail silently — cert-manager chains breaking post-upgrade, Velero jobs reporting success without executing — the impact is immediate and customer-facing.
To address this, we built a Kubernetes-native testing framework using Testkube that validates our full infrastructure stack on every GitOps-triggered change. Tests are defined as Kubernetes CRDs, integrated into our Flux delivery pipeline, and cover TLS validation, policy enforcement, secret sync, backup integrity, and add-on health across the stack.
This session walks through our test architecture, the specific failure classes we catch, and how we operationalized infrastructure testing as a first-class part of our platform engineering workflow — not an afterthought.
Submitted to Platform Engineering Day (KubeCon NA 2026 co-located event).
Audience: platform and GitOps engineers operating multi–CNCF add-on stacks.
When Infrastructure Breaks in Production: How EarnIn Brought Testing to the Full CNCF Stack
EarnIn runs 15+ CNCF add-ons (including Flux, Karpenter, Kyverno, cert-manager, Linkerd, external-secrets-operator, Velero, and more) on a high-availability platform where infrastructure failure directly affects people's access to their earnings.
After catching too many issues in production — cert-manager chains breaking silently after upgrades, Velero backup jobs completing without actually running — we built an in-cluster infrastructure testing framework using Testkube, wired directly into our Flux GitOps pipeline.
This session covers how we model infrastructure tests as Kubernetes CRDs, how quality gates fire on every GitOps-triggered change, and which failure classes we catch across our CNCF stack. We'll share real test patterns, the architecture that makes it work, and the lessons from operationalizing infrastructure testing at a fintech company where "it worked in staging" is not good enough.
Submitted to KubeCon NA 2026 — Main Track (Application Delivery) and Platform Engineering Day. Case study;
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