I work on Kubernetes-based delivery, infrastructure automation, cloud observability, and software supply chain security. My backend engineering background helps me connect application behavior with infrastructure and operational troubleshooting.
·CKA | Certified Kubernetes Administrator · AZ-104 | Microsoft Certified: Azure Administrator Associate
LinkedIn · Azure AKS project · GCP security reference
A Terraform-managed AKS reference environment with Argo CD workload reconciliation and Azure-native telemetry backends.
- Infrastructure and delivery: AKS, ACR, Terraform, Helm, Argo CD, and GitHub Actions. CI promotes an internal canary image through Git rather than acting as a second Kubernetes deployment controller.
- Observability: OpenTelemetry, Azure Monitor, Log Analytics, Managed Prometheus, and Container Insights.
- Recorded validation: 17 ready demo deployments in the main release; a checkout trace across 12 services in a separate temporary capture.
Source and architecture · Validation evidence · Scope and limitations
The upstream OpenTelemetry Demo supplies the application workload. My work focuses on platform integration, deployment, configuration, and validation.
A preserved GCP reference implementation connecting artifact identity, reviewed deployment state, admission enforcement, and runtime detection.
- Artifact trust: GitHub OIDC / GCP Workload Identity Federation, Cosign keyless signing, SPDX SBOM, and SLSA provenance attestations.
- Deployment and admission: digest-pinned GitOps delivery through Argo CD with Kyverno checks against the configured trust contract.
- Recorded validation: trusted-image admission; rejection of unsigned images and initContainers in the protected scope; rejection under incorrect trust expectations; Falco detection of controlled shell execution.
Preserved GCP source · Validation record · Threat model and boundaries
This work integrates and extends credited upstream components. The links
above deliberately target the GCP snapshot: current main contains an Azure
implementation, and the GCP evidence does not validate that newer code path.
My Kubernetes reference notes, organized around concepts, failure patterns, troubleshooting, and security considerations developed during CKA/CKS study.
| Area | Tools and concepts |
|---|---|
| Infrastructure | Azure, AKS, GCP, GKE, Terraform, Linux, networking |
| Delivery | Kubernetes, Docker, Helm, Argo CD, GitHub Actions, GitOps |
| Observability | OpenTelemetry, Azure Monitor, Log Analytics, Managed Prometheus, Container Insights |
| Security | OIDC, workload identity, Cosign, SBOM/provenance, Kyverno, Falco, Trivy, Semgrep |
| Backend foundation | Node.js, TypeScript, Fastify, PostgreSQL, Redis, BullMQ, Sequelize |
I keep infrastructure ownership separate from workload reconciliation, test negative security cases instead of showing only successful deployments, and record what the evidence does—and does not—prove.
My repositories describe recorded validation runs, not an always-on service, a production SLA, or an unqualified security guarantee.
Software engineering internship experience at Easyhyre, spanning backend systems, containerized delivery, and troubleshooting. BCA, CSJMU, Kanpur.
Seeking DevOps and Cloud Engineer opportunities focused on Kubernetes, infrastructure as code, delivery automation, observability, and security.