<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ritesh Sonawane</title><link>https://riteshsonawane.com/</link><description>Recent content on Ritesh Sonawane</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://riteshsonawane.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Types of LLM Explained: Dense, MoE, and Everything In Between</title><link>https://riteshsonawane.com/blog/llm-models/</link><pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/llm-models/</guid><description>&lt;p&gt;Ask someone what model they&amp;rsquo;re running and they&amp;rsquo;ll usually give you a name, Llama, GPT-4, DeepSeek. Ask them what architecture that model actually uses and why it was picked, and the conversation usually stalls.&lt;/p&gt;
&lt;p&gt;That gap matters. The architecture behind a model decides how it processes tokens, how much GPU memory it eats, how fast it responds, and what kind of hardware it wants. Two models with similar benchmark scores can have completely different cost and latency profiles once you look under the hood. If you work in AI infrastructure, this is the layer where your capacity planning, your hardware choices, and your cost per token all actually come from.&lt;/p&gt;</description></item><item><title>LLM Inference KPIs Every SRE Should Know</title><link>https://riteshsonawane.com/blog/llms-inference-kpis/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/llms-inference-kpis/</guid><description>&lt;h2 id="understanding-llm-inference-kpis-from-ttft-to-kv-cache"&gt;Understanding LLM Inference KPIs: From TTFT to KV Cache&lt;/h2&gt;
&lt;p&gt;Monitoring LLM inference is not like monitoring a web service. The metrics are different, the failure modes are different, and the relationship between what you measure and what the user experiences is more indirect. This post covers the core KPIs, what they actually measure, and how to reason about them operationally.&lt;/p&gt;
&lt;h2 id="first-understand-the-two-phases"&gt;First, Understand the Two Phases&lt;/h2&gt;
&lt;p&gt;Every LLM inference request goes through two distinct phases. If you do not understand the difference, the metrics will not make sense.&lt;/p&gt;</description></item><item><title>Kubernetes Gateway API Inference Extension</title><link>https://riteshsonawane.com/blog/k8s-gateway-api-inference/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/k8s-gateway-api-inference/</guid><description>&lt;h2 id="kubernetes-gateway-api-inference-extension-what-it-is-and-why-it-matters"&gt;Kubernetes Gateway API Inference Extension: What It Is and Why It Matters&lt;/h2&gt;
&lt;p&gt;If you are running LLM workloads on Kubernetes today, you have almost certainly hit the same wall. Your standard Ingress or Gateway routes traffic to pods based on HTTP path or headers. Round-robin distributes load across replicas. Everything looks fine from the control plane perspective. But your GPU utilization is uneven, some replicas are getting hammered while others sit idle, latency is unpredictable, and you have no way to differentiate a low-latency interactive chat request from a background batch job that can afford to wait.&lt;/p&gt;</description></item><item><title>NVIDIA DSX</title><link>https://riteshsonawane.com/blog/nvidia-dsx/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/nvidia-dsx/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;For years, building an AI data center meant assembling a puzzle from dozens of vendors, each speaking a different language. Chips from one company, software from another, cooling from a third, and a facility design that nobody had fully validated end to end. The result was expensive guesswork at massive scale.&lt;/p&gt;
&lt;p&gt;NVIDIA&amp;rsquo;s answer to this is the &lt;strong&gt;DSX platform&lt;/strong&gt;, announced at GTC Taipei on May 31, 2026. It is a full-stack, codesigned framework that gives infrastructure builders a single validated playbook to design, deploy, and operate AI factories at scale. The goal is simple: turn every megawatt into more intelligence, at the lowest possible token cost.&lt;/p&gt;</description></item><item><title>ndots in Kubernetes</title><link>https://riteshsonawane.com/blog/ndots-in-kubernetes/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/ndots-in-kubernetes/</guid><description>&lt;p&gt;Let&amp;rsquo;s see how the &lt;code&gt;ndots&lt;/code&gt; option works in Kubernetes.&lt;/p&gt;
&lt;p&gt;In Kubernetes, we connect to running pods either directly or via a Kubernetes Service. This post focuses on how service DNS resolution actually works under the hood.&lt;/p&gt;
&lt;h2 id="the-resolvconf-file"&gt;The resolv.conf file&lt;/h2&gt;
&lt;p&gt;In Linux, &lt;code&gt;/etc/resolv.conf&lt;/code&gt; is used by the &lt;a href="https://man7.org/linux/man-pages/man3/resolver.3.html"&gt;system resolver&lt;/a&gt; for domain name resolution. Kubernetes automatically injects this file into every pod with the configuration needed to resolve services inside the cluster.&lt;/p&gt;
&lt;p&gt;Here is an example from a CNPG cluster pod running in the &lt;code&gt;database&lt;/code&gt; namespace:&lt;/p&gt;</description></item><item><title>Celery to Argo Workflows</title><link>https://riteshsonawane.com/blog/celery-to-argoworkflows/</link><pubDate>Tue, 09 Dec 2025 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/celery-to-argoworkflows/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;AI jobs often run for long periods on expensive hardware like GPUs. When a job fails halfway, you don&amp;rsquo;t just lose progress—you waste valuable time and costly resources. Workflow orchestration solves this by providing fault tolerance, letting you break complex tasks into manageable steps, set dependencies, and recover from failures. This is especially critical in machine learning, where robust, efficient execution is paramount.&lt;/p&gt;</description></item><item><title>Scaling Prometheus with Thanos</title><link>https://riteshsonawane.com/blog/scaling-prometheus-to-thanos/</link><pubDate>Tue, 22 Jul 2025 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/scaling-prometheus-to-thanos/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Observability is a crucial pillar of any application, and monitoring is an essential component of it. Having a well-suited, robust monitoring system is crucial. It can help you detect issues in your application and provide insights once it is deployed. It aids in performance, resource management, and observability. Most importantly, it can help you save costs by identifying issues in your infrastructure. One of the most popular tools in monitoring is &lt;a href="https://prometheus.io/"&gt;Prometheus&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>100 TB from InfluxDB to Grafana Mimir</title><link>https://riteshsonawane.com/blog/migrate-influx-to-mimir/</link><pubDate>Mon, 07 Apr 2025 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/migrate-influx-to-mimir/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft!&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Observability is the backbone of any modern infrastructure, enabling organizations to monitor system health, optimize performance, and ensure seamless operations. However, when legacy observability systems reach their limits—whether due to scalability challenges, high costs, or lack of vendor support—businesses must pivot to more future-proof solutions.&lt;/p&gt;
&lt;p&gt;The migration presented a unique set of challenges: handling seven years of monitoring data (roughly 100TB of uncompressed data), complex migration as there is no direct support to migrate from InfluxDB to Grafana Mimir, Grafana dashboards rewrite from InfluxQL to PromQL format for 100s of dashboards. In this blog, we’ll walk through the entire migration process, the challenges faced, and the architectural choices that enabled a seamless transition to Grafana Mimir.&lt;/p&gt;</description></item><item><title>Overview of gRPC</title><link>https://riteshsonawane.com/blog/overview-of-grpc/</link><pubDate>Sun, 09 Feb 2025 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/overview-of-grpc/</guid><description>&lt;p&gt;Taking HTTP/2 to next Level&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before understanding gRPC lets see what is RPC&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-is-rpcremote-procedure-call"&gt;What is RPC(remote procedure call)?&lt;/h2&gt;
&lt;p&gt;RPC is a communication protocol which allows a program to execute functions on a remote server as if it was a local function. RPC simplifies distributed computing by hiding network complexity.&lt;/p&gt;
&lt;p&gt;Consider you have a program calling a function, but here this function execution is on a remote server. The program which is calling this function does needs to know anything about the network details.&lt;/p&gt;</description></item><item><title>Monitoring with Prometheus</title><link>https://riteshsonawane.com/blog/monitoring-with-prometheus/</link><pubDate>Thu, 04 Jul 2024 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/monitoring-with-prometheus/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Monitoring is the lifeline that ensures the seamless operation of systems, applications, and networks. Whether managing a small startup or a large enterprise, the ability to monitor infrastructure in real time is crucial for maintaining performance, ensuring reliability, and quickly resolving issues before they escalate. The average cost of downtime in IT industry as per &lt;a href="https://www.pingdom.com/outages/average-cost-of-downtime-per-industry/"&gt;Pingdom&lt;/a&gt; is between $5600 to $9600 per minute and as more and more digitization happens, it is going to increase further.&lt;/p&gt;</description></item><item><title>Streamlining Model Lifecycle with KubeRay</title><link>https://riteshsonawane.com/blog/kuberay/</link><pubDate>Fri, 24 May 2024 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/kuberay/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft!&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;As the demand for ML and LLM models continues to grow, so does the need for reliability and scalability. Integrating Kubernetes into model development emerges as a powerful solution. By leveraging Kubernetes, we can streamline the process of model development, decrease costs, and enhance model reliability. This can be achieved using Ray on Kubernetes. But before that, let&amp;rsquo;s take a look at the lifecycle of an ML model.&lt;/p&gt;</description></item><item><title>Making Kubernetes Simple with Talos</title><link>https://riteshsonawane.com/blog/talos/</link><pubDate>Tue, 07 May 2024 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/talos/</guid><description>&lt;p&gt;&lt;strong&gt;This blog is based on my work at CloudRaft! &lt;em&gt;(My first blog at CloudRaft)&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes marks its 10th anniversary this year with the release of version v1.30.0, solidifying its status as the cloud platform of choice. Managed Kubernetes clusters like EKS, GKS and AKS represent 73% of the total cluster, remaining 27% are self-managed as per &lt;a href="https://assets.dynatrace.com/en/docs/wp/bae3218-wp-kubernetes-in-the-wild-en.pdf?_ga=2.202268564.403052509.1714528198-1455211400.1714528198"&gt;Dynatrace&lt;/a&gt;. The last decade has been an era of public cloud but due to increasing costs, some businesses are trying to find a balance with the hybrid cloud. Approximately 76% of organizations now leverage multiple clouds which is a combination of public and private clouds as per &lt;a href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmware-ebook-state-of-kubernetes.pdf"&gt;VMware&lt;/a&gt;. Kubernetes allows us to build a multi-cloud and private cloud layer on the hardware of choice and in a cost-effective way without committing to one specific cloud.&lt;/p&gt;</description></item><item><title>About</title><link>https://riteshsonawane.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/about/</guid><description>&lt;h2 id="experience"&gt;Experience&lt;/h2&gt;
&lt;h3 id="site-reliability-engineer--cloudraft"&gt;Site Reliability Engineer — CloudRaft&lt;/h3&gt;
&lt;p&gt;April 2024 – March 2026 • Remote&lt;/p&gt;
&lt;p&gt;Owned infrastructure architecture and platform engineering across 10+ client environments spanning telecom, AI/ML, fintech, and enterprise SaaS.&lt;/p&gt;
&lt;h4 id="enkryptai--aiml-infrastructure--production-operations"&gt;EnkryptAI — AI/ML Infrastructure &amp;amp; Production Operations&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Owned complete AWS EKS infrastructure and VPC-level architecture, serving as DevOps Lead for enterprise client deployments&lt;/li&gt;
&lt;li&gt;Architected and developed 3 cloud-agnostic Helm Charts (EnkryptAI Stack, Platform Stack, Platform Core) to orchestrate 70+ microservices in fully air-gapped multi-cloud deployments (AWS, GCP, Azure) with GPU node support and VRAM-based scheduling&lt;/li&gt;
&lt;li&gt;Onboarded 2 enterprise clients on AKS and EKS environments&lt;/li&gt;
&lt;li&gt;Re-architected Redteaming job orchestration by migrating from Celery-based execution to a Kubernetes-native stack using Argo Workflows, Argo Events, and NATS&lt;/li&gt;
&lt;li&gt;Created a Golang-based container entrypoint script, reducing Kubernetes pod startup time from 5 minutes to 30 seconds for a NextJS application&lt;/li&gt;
&lt;li&gt;Managed on-call rotation using incident.io for guardrails and red-teaming services, ensuring production uptime and incident response&lt;/li&gt;
&lt;li&gt;Deployed production guardrails application on NVIDIA A30/H100 GPUs using NVIDIA GPU Operator&lt;/li&gt;
&lt;li&gt;Resolved critical compatibility and deployment issues with NVIDIA GPU Operator on Azure Kubernetes Service (AKS)&lt;/li&gt;
&lt;li&gt;Deployed on-prem OpenFGA integrated with CloudNativePG (CNPG) as the backing PostgreSQL database to implement fine-grained, scalable RBAC across the platform&lt;/li&gt;
&lt;li&gt;Migrated Elasticsearch to OpenSearch using the OpenSearch Kubernetes Operator and transitioned Kibana dashboards to OpenSearch Dashboards, ensuring continuity of audit logging&lt;/li&gt;
&lt;li&gt;Customized and deployed Supabase Helm Chart with CloudNativePG (CNPG) to migrate Supabase from managed cloud to on-prem VPC deployment within air-gapped enterprise environments&lt;/li&gt;
&lt;li&gt;Implemented DevSecOps practices by integrating SBOM generation and Grype-based vulnerability scanning into CI/CD pipelines, with automated Slack alerts for high-severity findings&lt;/li&gt;
&lt;li&gt;Configured Devspace for developers enabling rapid deployment to AWS GPU nodes&lt;/li&gt;
&lt;li&gt;Supported SOC 2 and ISO 27001 compliance initiatives&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="composio--enterprise-saas-platform--customer-onboarding"&gt;Composio — Enterprise SaaS Platform &amp;amp; Customer Onboarding&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Implemented Replicated as enterprise portal for customer onboarding, reducing onboarding time from days to 1 hour&lt;/li&gt;
&lt;li&gt;Migrated existing clients to Replicated platform, enabling centralized release management and automated updates&lt;/li&gt;
&lt;li&gt;Wrote preflight and postflight validation checks for installation reliability&lt;/li&gt;
&lt;li&gt;Built multi-channel CI/CD pipeline with GitHub Actions supporting Unstable, Stable, and Nightly releases&lt;/li&gt;
&lt;li&gt;Led client onboarding for 6+ production environments across AWS EKS and GCP GKE&lt;/li&gt;
&lt;li&gt;Customized Temporal Helm charts for client-specific requirements&lt;/li&gt;
&lt;li&gt;Automated deployment of unstable Replicated releases to GKE for continuous testing&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="skyswitch--100tb-monitoring-migration-telecom"&gt;SkySwitch — 100TB Monitoring Migration (Telecom)&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Led migration of 100TB+ InfluxDB data to Grafana Mimir with zero downtime&lt;/li&gt;
&lt;li&gt;Built custom Golang conversion tool to transform InfluxDB data to OpenMetrics format for Grafana Mimir&lt;/li&gt;
&lt;li&gt;Migrated 1000+ Grafana dashboards from InfluxQL to PromQL&lt;/li&gt;
&lt;li&gt;Re-architected single-tenant Mimir to multi-tenant model, reducing compactor startup time from hours to 5 minutes&lt;/li&gt;
&lt;li&gt;Reduced infrastructure compute and memory usage by 30%&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="neevcloud--gpu-cloud-platform"&gt;NeevCloud — GPU Cloud Platform&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Built production-grade GPU cloud platform on bare-metal Kubernetes (kubeadm) with KubeVirt and NVIDIA GPUs&lt;/li&gt;
&lt;li&gt;Developed Golang-based VM provisioning API with GPU-aware scheduling and inventory validation logic&lt;/li&gt;
&lt;li&gt;Implemented custom x-api-key authentication middleware for VLLM model endpoints using Traefik&lt;/li&gt;
&lt;li&gt;Configured Cilium CNI to assign public IPs to KubeVirt VMs&lt;/li&gt;
&lt;li&gt;Resolved GPU passthrough issues and fixed VM network persistence using KubeMacPool&lt;/li&gt;
&lt;li&gt;Enforced AWS-style resource quotas to prevent over-provisioning&lt;/li&gt;
&lt;li&gt;Achieved 99.9%+ uptime for commercial GPU workloads with CI/CD via GitHub Actions, ArgoCD, and Harbor&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="rezolveai--enterprise-observability--cost-optimization"&gt;Rezolve.ai — Enterprise Observability &amp;amp; Cost Optimization&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Designed and deployed an observability stack across 4 production AKS clusters using Prometheus, Grafana, OpenTelemetry Operator, Loki, and Tempo&lt;/li&gt;
&lt;li&gt;Enabled RED metrics and service graphs for production services&lt;/li&gt;
&lt;li&gt;Identified infrastructure inefficiencies using Steampipe/Powerpipe, delivering $36,000 annual cost savings&lt;/li&gt;
&lt;li&gt;Led Kubernetes version upgrades to v1.31 across all clusters&lt;/li&gt;
&lt;li&gt;Planned and executed Jenkins server upgrade&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="ditto--multi-cloud-byoc-platform"&gt;Ditto — Multi-Cloud BYOC Platform&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Using Cluster API, provisioned kubeadm clusters on client environments across AWS (CAPA), GCP (CAPG), and Azure (CAPZ)&lt;/li&gt;
&lt;li&gt;Developed custom Golang migration script for transition from MachinePool to MachineDeployment for AWS and GCP based Kubernetes clusters&lt;/li&gt;
&lt;li&gt;Automated deployment of Velero, Cluster Autoscaler, and Node Problem Detector using ArgoCD ApplicationSets across multi-cloud environments&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="clika--ai-job-orchestration-platform"&gt;Clika — AI Job Orchestration Platform&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Built Golang-based Kubernetes job scheduler with credit-based billing and a ledger system&lt;/li&gt;
&lt;li&gt;Implemented S3-compatible storage integration for ML model outputs with access controls&lt;/li&gt;
&lt;li&gt;Integrated VictoriaMetrics and VictoriaLogs for real-time job observability with custom API endpoints&lt;/li&gt;
&lt;li&gt;Provisioned GKE infrastructure via Terraform with CI/CD automation using ArgoCD and GitHub Actions&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="iff--enterprise-authentication-integration-fortune-500"&gt;IFF — Enterprise Authentication Integration (Fortune 500)&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Implemented organization-wide SAML-based authentication for ArgoCD, enhancing secure access management across enterprise deployments&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="drdroid--cicd-modernization"&gt;DrDroid — CI/CD Modernization&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Modernized bash-based deployments to production-grade CI/CD pipeline using GitHub Actions and ArgoCD with Image Updater&lt;/li&gt;
&lt;li&gt;Set up Metabase for database analytics and insights&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="kubernetes-homelab"&gt;Kubernetes Homelab&lt;/h4&gt;
&lt;p&gt;I run a multi-node k3s cluster at &lt;a href="http://pidoku.co.in/"&gt;pidoku.co.in&lt;/a&gt; to test cloud-native infrastructure patterns before using them in production.&lt;/p&gt;</description></item><item><title>Work with me</title><link>https://riteshsonawane.com/hire/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/hire/</guid><description>&lt;p&gt;I am available for remote SRE, platform engineering, DevOps, and Kubernetes infrastructure work.&lt;/p&gt;
&lt;h2 id="what-i-do"&gt;What I do&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Kubernetes platforms.&lt;/strong&gt; Production clusters on managed Kubernetes (EKS, GKE, AKS) and on bare metal with kubeadm, Talos, and k3s. Cloud-agnostic Helm charts, including fully air-gapped multi-cloud installs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Observability.&lt;/strong&gt; Prometheus, Grafana, Thanos, Mimir, Loki, Tempo, OpenTelemetry, VictoriaMetrics. RED metrics, service graphs, and alerting that people actually act on.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Migrations.&lt;/strong&gt; Moving large systems without downtime — time-series databases, cloud-to-cloud, orchestration engines, logging stacks.&lt;/p&gt;</description></item></channel></rss>