<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://nishalrai.com.np/</id><title>Nishal Rai</title><subtitle>NISHAL RAI | F5-BIGIP-CTS-ASM | F5-BIGIP-201 | nishalrai2056@gmail.com Kathmandu, Nepal</subtitle> <updated>2026-04-18T22:00:24+05:45</updated> <author> <name>Nishal Rai</name> <uri>https://nishalrai.com.np/</uri> </author><link rel="self" type="application/atom+xml" href="https://nishalrai.com.np/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://nishalrai.com.np/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Nishal Rai </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>When DDoS Protection Starts Hurting Operations</title><link href="https://nishalrai.com.np/posts/when-ddos-protection-starts-hurting-operations/" rel="alternate" type="text/html" title="When DDoS Protection Starts Hurting Operations" /><published>2026-04-17T08:40:00+05:45</published> <updated>2026-04-17T08:40:00+05:45</updated> <id>https://nishalrai.com.np/posts/when-ddos-protection-starts-hurting-operations/</id> <content src="https://nishalrai.com.np/posts/when-ddos-protection-starts-hurting-operations/" /> <author> <name>nishalrai</name> </author> <category term="DDoS" /> <category term="Automation" /> <summary> In DDoS defense, getting the appliance deployed is rarely the end of the story. In many environments especially in telecom, banking and large distributed infrastructures, the real challenge starts after the platform is already in place. Detection begins to work, alerts begin to flow, baselines start learning, and then operations team realize something important: the appliance is detecting, but ... </summary> </entry> <entry><title>Lightweight ELK Deployment on K3s for F5 Security Logs</title><link href="https://nishalrai.com.np/posts/lightweight-elk-deployment-k3s-f5-security-log/" rel="alternate" type="text/html" title="Lightweight ELK Deployment on K3s for F5 Security Logs" /><published>2025-05-31T18:40:00+05:45</published> <updated>2025-05-31T18:40:00+05:45</updated> <id>https://nishalrai.com.np/posts/lightweight-elk-deployment-k3s-f5-security-log/</id> <content src="https://nishalrai.com.np/posts/lightweight-elk-deployment-k3s-f5-security-log/" /> <author> <name>nishalrai</name> </author> <category term="Kubernetes" /> <category term="ELK" /> <summary> F5 Networks’ BIG-IP systems are widely used for application delivery and security, but their local logging capabilities are constrained. With a storage limit of either 3 million requests or 2 GB, logs are archived once either threshold is reached, retaining only the most recent entries. Each daemon and feature (e.g., security, bot, or DoS event logs) shares this quota, making local storage insu... </summary> </entry> <entry><title>Installing Docker Desktop on a Drive Other Than C drive</title><link href="https://nishalrai.com.np/posts/installing-docker-desktop/" rel="alternate" type="text/html" title="Installing Docker Desktop on a Drive Other Than C drive" /><published>2025-05-31T18:40:00+05:45</published> <updated>2025-06-01T01:32:13+05:45</updated> <id>https://nishalrai.com.np/posts/installing-docker-desktop/</id> <content src="https://nishalrai.com.np/posts/installing-docker-desktop/" /> <author> <name>nishalrai</name> </author> <category term="Cloud Native" /> <category term="Docker" /> <summary> By default, Docker Desktop installs itself on the C: drive, but if you’re tight on space or prefer keeping your dev tools on a different partition, you can install Docker Desktop to another drive (like D:) — even when using WSL2 under the hood. This will be a step-by-step guide to help you get it done cleanly and without surprises during the installation of the docker desktop. Prerequisites ... </summary> </entry> <entry><title>Introducing Ingress Controllers - An Essential Insights</title><link href="https://nishalrai.com.np/posts/ingress-controller/" rel="alternate" type="text/html" title="Introducing Ingress Controllers - An Essential Insights" /><published>2024-03-05T18:40:00+05:45</published> <updated>2024-09-18T13:52:47+05:45</updated> <id>https://nishalrai.com.np/posts/ingress-controller/</id> <content src="https://nishalrai.com.np/posts/ingress-controller/" /> <author> <name>nishalrai</name> </author> <category term="Cloud Native" /> <category term="Microservice" /> <summary> Most of us have heard about the ingress controller at least once when Kubernetes was the topic of the talk and I aim to demystify a fundamental understanding of the ingress controller in this post by answering: What is an ingress controller? Why do we need an ingress controller in the first place? How does the ingress controller work? Before we begin to learn about ingress controllers... </summary> </entry> <entry><title>Setup your own Kubernetes Cluster</title><link href="https://nishalrai.com.np/posts/kubernetes-setup/" rel="alternate" type="text/html" title="Setup your own Kubernetes Cluster" /><published>2024-02-27T18:40:00+05:45</published> <updated>2024-09-18T13:52:47+05:45</updated> <id>https://nishalrai.com.np/posts/kubernetes-setup/</id> <content src="https://nishalrai.com.np/posts/kubernetes-setup/" /> <author> <name>nishalrai</name> </author> <category term="Cloud Native" /> <category term="Microservice" /> <summary> The best way to deepen your understanding is to build, break, and fix it—at least, this is how my learning works. After delving into videos, sifting through documentation, and scouring online posts, I’ve managed to glean a high-level understanding of container orchestration within Kubernetes clusters. Yet, the burning question persists: How does Kubernetes wield its management magic? Well, you... </summary> </entry> </feed>
