Delhi, India

© 2026 Vedops

Open to: collaboration

DevOps Engineer Portfolio

Vedant Kalia

Cloud and DevOps infrastructure photo
Cloud and DevOps infrastructure photo
Cloud and DevOps infrastructure photo

+

building & experimenting

Let's Connect

Happy to talk tech, exchange ideas, and explore interesting problems.

© 2026

Microsoft Azure
Kubernetes
Docker
Terraform
Linux
GitHub Actions
Prometheus
Grafana
Cloudflare
LESS NOISE MORE SIGNAL ·
[THREE FOCUS AREAS]

Cloud & Infrastructure

Designing resilient cloud environments on Azure and Kubernetes with infrastructure as code.

CI/CD & Automation

Building pipelines that deliver code to production quickly, safely, and repeatably.

Monitoring & Observability

Instrumenting systems so performance, security, and reliability are always visible.

Cloud infrastructure architecture

Cloud

I architect cloud environments on Azure and Kubernetes with infrastructure as code. Reproducible, auditable environments are the foundation of reliable platforms.

CI/CD

I build pipelines and automation that turn commits into safe, repeatable releases. Every change is validated, tested, and delivered consistently across environments.
Monitoring dashboards on screen

SRE

I instrument systems with monitoring, logging, and alerting so reliability stays observable. Metrics and logs turn guesswork into data, incidents get caught early, and root causes stay clear.

With focus on Microsoft Azure, Kubernetes, and automation-first engineering

My Focus

The Technology I Work With Every Day

Clouddrove

[Jun 2024 - Current]

Associate Devops Engineer

Building and operating cloud infrastructure on Azure and Kubernetes (AKS) with a focus on reliability and cost efficiency.

Ahead Websoft Technologies

[June 2022 - Sept 2022]

AWS Intern

Worked day-to-day with the senior system administrators keeping the Linux servers running, handling access control, and watching performance numbers.

Freelancer

[Sep 2020 - Mar 2021]

Freelancer

Looked after Linux servers for clients, answered their calls and tickets, and made sure nothing stayed down long.

My Focus

Areas of Expertise

Cloud Infrastructure

DevOps & CI/CD

Automation & Observability

Vedops globe icon

I’m Vedant Kalia, a DevOps and Cloud engineer. I design cloud architecture on Microsoft Azure, manage Kubernetes clusters, and turn manual operations into repeatable automation. I’m always learning, experimenting, and sharing what I build. Find out more about me.

Cloud Infrastructure

CI/CD & Automation

Kubernetes & Containers

DevOps Cloud Azure Kubernetes CI/CD Automation DevSecOps Infrastructure as Code Linux Observability Open Source DevOps Cloud Azure Kubernetes CI/CD Automation DevSecOps Infrastructure as Code Linux Observability Open Source
Portfolio

My Work Speaks for Itself

A selection of projects & experiments

Verified Stack

Essential Tools I Use

I work mainly in the Microsoft Azure and Kubernetes ecosystem. My focus is infrastructure as code, automation-first delivery, and observability.

Microsoft Azure
Microsoft Azure

Cloud Platform

Kubernetes
Kubernetes

Container Orchestration

Docker
Docker

Containerization

Terraform
Terraform

Infrastructure as Code

Linux
Linux

Operating System

GitHub Actions
GitHub Actions

CI/CD Automation

Prometheus
Prometheus

Monitoring

Grafana
Grafana

Observability Dashboards

Cloudflare
Cloudflare

Security & Performance

With expertise in Azure, Kubernetes, and automation & monitoring

Journal

Notes From
My Engineering Journey

Support Guide

Helpful Answers to
Your Common Questions

  • About Me
  • Client Testimonials
  • Contact Information
  • Project Showcase
All FAQs
What do you do?

I'm Vedant Kalia, a DevOps and Cloud engineer. I work mostly in the Microsoft Azure and Kubernetes ecosystem: designing cloud infrastructure, building CI/CD pipelines, and automating operations so systems stay reliable.

What are your main areas of expertise?

Cloud infrastructure on Azure and Kubernetes (AKS), CI/CD and release automation, infrastructure as code (Terraform, Bicep), Linux and networking, plus monitoring and observability.

How do you approach problem-solving?

I start from the system: I look at the evidence, find the root cause, apply the smallest change that fixes it, and then automate away the repetition so the problem does not come back.