<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on 📋 JayJay's DevOps Diaries ..</title><link>http://halfknown.co.uk/categories/networking/</link><description>Recent content in Networking on 📋 JayJay's DevOps Diaries ..</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 02 May 2026 08:58:59 +0000</lastBuildDate><atom:link href="http://halfknown.co.uk/categories/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Atrophy from disuse - Forgotten Debug Skills</title><link>http://halfknown.co.uk/pages/iloveit/</link><pubDate>Fri, 05 Jun 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/iloveit/</guid><description>&lt;p>Growing up, my mother repeatedly said &lt;strong>&amp;ldquo;If you dont blow your trumpet, it would rust!!&amp;rdquo;&lt;/strong>&lt;/p>
&lt;p>It happens to all of us. You spend years in the trenches of systems administration, mastering the intricacies of &lt;strong>BIND 9&lt;/strong>, manually tweaking &lt;code>MX records&lt;/code>, and living inside &lt;code>nslookup&lt;/code>, &lt;code>getent&lt;/code>, &lt;code>host&lt;/code> and &lt;code>dig&lt;/code> commands. Then, your career shifts. You move into orchestrating &lt;strong>Docker &amp;amp; CICD&lt;/strong>, managing &lt;strong>IaC with Terraform&lt;/strong>, and focusing on cloud-native abstractions.&lt;/p>
&lt;p>Suddenly, you find yourself staring at a simple DNS issue, and it hits you: the muscle memory for the &amp;ldquo;basics&amp;rdquo; has started to fade.&lt;/p></description></item><item><title>Linkerd + Deployment Strategy - PART 1 {Canary}</title><link>http://halfknown.co.uk/pages/servicemesh-linkered/</link><pubDate>Sun, 24 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/servicemesh-linkered/</guid><description>&lt;h3 id="-------------if-youer-seeing-this--------">**** 🚧 IF YOU&amp;rsquo;ER SEEING THIS 🚧 ****&lt;/h3>
&lt;h4 id="---this-is-a-polite-notice-that-this-article-is-a-work-in-progress--">*** 🚦 THIS IS A POLITE NOTICE THAT THIS ARTICLE IS A WORK-IN-PROGRESS 🚥 ****&lt;/h4>
&lt;p>&lt;em>The article is currently being tweaked, drafted and is not yet complete. I’m sharing it early to document my process, so feel free to take a look at the current progress. I expect to finalize the content in my next commit&lt;/em>&lt;/p>
&lt;h4 id="thanks-for-reading-">THANKS FOR READING 🧐!&lt;/h4>
&lt;h4 id="do-enjoy-yourself-in-the-process-">DO ENJOY YOURSELF IN THE PROCESS 😇!&lt;/h4>
&lt;h1 id="heading">************&lt;/h1>
&lt;hr>
&lt;h1 id="introducktion">Introducktion&lt;/h1>
&lt;p>The other day, I shared a concern in a WhatsApp group comprised of some super advanced DevOps Engineers as well as aspiring Linux Administrators. There I was, pouring my heart out around the topic of 
&lt;a href="http://halfknown.co.uk/pages/service-mesh/">Service Mesh&lt;/a>, (Istio, and Linkerd). How all these subjects were all intertwined and downright confusing. In the course of the debate, I’d later realised I would have to throw in a bit of 
&lt;a href="http://halfknown.co.uk/pages/deployment-strategies/">Deployment Strategies&lt;/a> just to fully grasp their concepts.&lt;/p></description></item><item><title>☸️ For the HELM of it - PART 2</title><link>http://halfknown.co.uk/pages/helm-charts-part2/</link><pubDate>Tue, 05 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/helm-charts-part2/</guid><description>&lt;h1 id="intro">Intro&lt;/h1>
&lt;p>In the last article, titled: 
&lt;a href="http://halfknown.co.uk/pages/helm-charts/">For the Helm of it&lt;/a>, I successfully demonstrated how to deploy a &lt;strong>single&lt;/strong> Web-Application - 
&lt;a href="http://halfknown.co.uk/pages/cool-docs">WebApps&lt;/a> at random from the 
&lt;a href="https://hub.docker.com/r/burgxy/webapps/" target="_blank" rel="noopener">DockerHub Artifactory&lt;/a> using Helm Charts templates.&lt;/p>
&lt;p>And by thus doing, we managed to demonstrate with Screenshots :&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Creating a Helm chart template&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Modifing the Helm template to accomodate a custom Web Application of our choosing&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Appended &lt;code>/etc/hosts&lt;/code> file to facilitate DNS resolution to hostnames &lt;strong>&lt;code>maltina.app1&lt;/code>&lt;/strong> and &lt;strong>&lt;code>maltina.app2&lt;/code>&lt;/strong>&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Enabling Ingress to accept external web traffic&lt;/p></description></item><item><title>☸️ For the HELM of it - PART 1</title><link>http://halfknown.co.uk/pages/helm-charts/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/helm-charts/</guid><description>&lt;h4 id="intro">Intro&lt;/h4>
&lt;p>In a cheeky 🥴 bid to demonstrate a simple app deployment 🧐 utilizing Helm Charts, 🤔 I would be plagiarising 
&lt;a href="https://www.linkedin.com/pulse/helm-template-chart-kubernetes-components-john-ikeson-lxxoe/" target="_blank" rel="noopener">a friends article&lt;/a> on Helm Charts that actaully got me started, provided the ground work and basic understanding on them.. I really loved his take on it.&lt;/p>
&lt;h1 id="-getting-the-hang-of--helm-charts-whats-cool--and-whats-not">🤓 Getting the hang of ☸️ HELM CHARTs: whats cool 😎 and whats not🥴..&lt;/h1>
&lt;hr>
&lt;p>Ok, the said friend of mine wrote this banging article about deploying an app using Helm Charts templates. And I really loved it. It was simple, concise and to the very point.&lt;/p></description></item><item><title>Ahh!!! Istio - Service Mesh</title><link>http://halfknown.co.uk/blog/2026-05-02-ahh-istio-service-mesh/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/blog/2026-05-02-ahh-istio-service-mesh/</guid><description>&lt;h1 id="please-give-me-a-moment--i-am-still-thinking-about-it-">Please give me a moment !! I am still thinking about it ..&lt;/h1>
&lt;pre>&lt;code> # 🚧 Under Construction 🚧
&lt;/code>&lt;/pre>
&lt;p>Hold Your Horses!You’ve stumbled upon a page that is currently being built.&lt;/p>
&lt;p>My &amp;ldquo;Construction Crew&amp;rdquo; (which is just me, with a cup of coffee and a dream) is working hard to get this page up and running.&lt;/p>
&lt;h2 id="-current-project-status">📉 Current Project Status:&lt;/h2>
&lt;pre>&lt;code>Task Status

Writingcontent ⏳ In Progress

Debugging my life choices 🛠️ Working on it

Proofreading ❌ Not started

Adding actual value 📉 Check back later
&lt;/code>&lt;/pre></description></item><item><title>Kubernetes Basics: Exposing a Pod with Service and Ingress – Follow-up Tutorial</title><link>http://halfknown.co.uk/blog/2026-05-02-kubernetes-basics-exposing-a-pod-with-service-and-ingress-follow-up-tutorial/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/blog/2026-05-02-kubernetes-basics-exposing-a-pod-with-service-and-ingress-follow-up-tutorial/</guid><description>&lt;h1 id="kubernetes-basics-exposing-a-pod-with-service-and-ingress">Kubernetes Basics: Exposing a Pod with Service and Ingress&lt;/h1>
&lt;p>This is a follow‑up tutorial to &lt;strong>&amp;ldquo;Kubernetes Basics: Running Pods&amp;rdquo;&lt;/strong>. We’ll take the Nginx Pod you already created and make it accessible both inside and outside your cluster — first with a Service, then with an Ingress so you can use a proper URL.&lt;/p>
&lt;hr>
&lt;nav id="TableOfContents">
 &lt;ul>
 &lt;li>&lt;a href="#kubernetes-basics-exposing-a-pod-with-service-and-ingress">Kubernetes Basics: Exposing a Pod with Service and Ingress&lt;/a>
 &lt;ul>
 &lt;li>&lt;a href="#-prerequisites">📋 Prerequisites&lt;/a>&lt;/li>
 &lt;/ul>
 &lt;/li>
 &lt;/ul>
&lt;/nav>

&lt;hr>
&lt;h2 id="-prerequisites">📋 Prerequisites&lt;/h2>
&lt;p>Before starting, ensure you have:&lt;/p></description></item><item><title>The concept of Deployment Strategies.</title><link>http://halfknown.co.uk/pages/deployment-strategies/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/deployment-strategies/</guid><description>&lt;h2 id="understanding-deployment-strategies">Understanding Deployment Strategies&lt;/h2>
&lt;p>In modern software engineering, a deployment strategy is the systematic approach used to release new application code to a production environment. These strategies serve as the bridge between development and end-user access, determining how updates are introduced while maintaining system stability.&lt;/p>
&lt;h3 id="why-deployment-strategies-are-important">Why Deployment Strategies are Important&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Risk Mitigation:&lt;/strong> Carefully selecting a deployment strategy helps minimize the impact of potential bugs or outages by limiting exposure to only a fraction of your user base.&lt;/li>
&lt;li>&lt;strong>Ensuring High Availability:&lt;/strong> Many strategies, such as Blue-Green or Rolling Updates, allow teams to perform deployments with zero or near-zero downtime, ensuring services remain accessible.&lt;/li>
&lt;li>&lt;strong>Rapid Feedback Loops:&lt;/strong> Strategies like A/B testing and Canary releases provide teams with real-time performance metrics and user feedback, allowing for data-driven decisions before a full-scale rollout.&lt;/li>
&lt;li>&lt;strong>Streamlined Recovery:&lt;/strong> Well-defined deployment patterns include clear rollback mechanisms, enabling teams to quickly revert to a stable version if a new release performs poorly.&lt;/li>
&lt;li>&lt;strong>Consistent Reliability:&lt;/strong> By automating the deployment process through these strategies, teams reduce the likelihood of human error, leading to more predictable and reliable software delivery.&lt;/li>
&lt;/ul>
&lt;p>&lt;img src="http://halfknown.co.uk/deploy-strategy/kuby-diagram.png" alt="Alt Text for accessibility">&lt;/p></description></item><item><title>The Magic of Service Mesh</title><link>http://halfknown.co.uk/pages/service-mesh/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/service-mesh/</guid><description>&lt;h1 id="service-mesh-architecture">Service Mesh Architecture&lt;/h1>
&lt;p>A Service Mesh is a dedicated infrastructure layer that handles service-to-service communication within a microservices architecture. Instead of your application code managing complex tasks like traffic routing, security, or observability, a service mesh offloads these responsibilities to a fleet of lightweight network proxies (often called &amp;ldquo;sidecars&amp;rdquo;) deployed alongside each service instance.&lt;/p>
&lt;p>&lt;img src="http://halfknown.co.uk/deploy-strategy/service-mesh.png" alt="Alt Text for accessibility">&lt;/p>
&lt;h2 id="why-do-we-need-a-service-mesh">Why do we need a Service Mesh?&lt;/h2>
&lt;p>As microservices architectures grow, managing communication between hundreds or thousands of services becomes overwhelming. A service mesh solves the following challenges:&lt;/p></description></item><item><title>THIS IS A TEMPLATE !! A template</title><link>http://halfknown.co.uk/stash/template/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/stash/template/</guid><description>&lt;h3 id="-------------if-youer-seeing-this--------">**** 🚧 IF YOU&amp;rsquo;ER SEEING THIS 🚧 ****&lt;/h3>
&lt;h4 id="---this-is-a-polite-notice-that-this-article-is-a-work-in-progress--">*** 🚦 THIS IS A POLITE NOTICE THAT THIS ARTICLE IS A WORK-IN-PROGRESS 🚥 ****&lt;/h4>
&lt;p>&lt;em>This article is currently being tweaked, drafted and is not yet complete. I’m sharing it early to document my process, so feel free to take a look at the current progress. I expect to finalize the content in my next commit&lt;/em>&lt;/p>
&lt;h4 id="thanks-for-reading-">THANKS FOR READING 🧐!&lt;/h4>
&lt;h4 id="do-enjoy-yourself-in-the-process-">DO ENJOY YOURSELF IN THE PROCESS 😇!&lt;/h4>
&lt;h1 id="heading">************&lt;/h1>
&lt;hr>
&lt;h1 id="kubernetes-basics-exposing-a-pod-with-service-and-ingress">Kubernetes Basics: Exposing a Pod with Service and Ingress&lt;/h1>
&lt;p>This is a follow‑up tutorial to &lt;strong>&amp;ldquo;Kubernetes Basics: Running Pods&amp;rdquo;&lt;/strong>. We’ll take the Nginx Pod you already created and make it accessible both inside and outside your cluster — first with a Service, then with an Ingress so you can use a proper URL.&lt;/p></description></item><item><title>WebApps - A cool Docker Image, for testing, debugging, training, and demonstration purposes.</title><link>http://halfknown.co.uk/pages/cool-docs/</link><pubDate>Sat, 02 May 2026 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/pages/cool-docs/</guid><description>&lt;p>Master the process of creating, versioning, and deploying customized Nginx Docker images. You will learn how to build tailored containers, push them to an artifact registry like DockerHub, and seamlessly pull them for use in Docker, Kubernetes, or any Infrastructure as Code environment. This configuration-driven approach allows for rapid, repeatable deployments—simply update the image version tag in your manifests to reuse the same infrastructure logic across different environments.&lt;/p>
&lt;h2 id="introducktion">INTRODUCkTION&lt;/h2>
&lt;hr>
&lt;p>
&lt;a href="https://hub.docker.com/r/burgxy/webapps/" target="_blank" rel="noopener">Webapps&lt;/a>- is a custom Nginx container, designed for &lt;strong>training, testing, and demonstration purposes&lt;/strong>. It provides an engaging, visual way to uniquely identify running applications via their &lt;strong>hostnames, IP addresses, and unique color themes&lt;/strong> based on each version.&lt;/p></description></item><item><title>Mother always said..'If you dont blow your trumpet, it would rust...'</title><link>http://halfknown.co.uk/stash/mother-said-copy/</link><pubDate>Thu, 02 May 2024 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/stash/mother-said-copy/</guid><description>&lt;p>It happens to all of us. You spend years in the trenches of systems administration, mastering the intricacies of BIND 9, manually tweaking MX records, and living inside getent and dig commands. Then, your career shifts. You move into orchestrating Kubernetes, managing IaC with Terraform, and focusing on cloud-native abstractions.&lt;/p>
&lt;p>Suddenly, you find yourself staring at a simple DNS issue, and it hits you: the muscle memory for the &amp;ldquo;basics&amp;rdquo; has started to fade.&lt;/p></description></item><item><title>Mother always said..'If you dont blow your trumpet, it would rust...'</title><link>http://halfknown.co.uk/stash/mother-said/</link><pubDate>Thu, 02 May 2024 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/stash/mother-said/</guid><description>&lt;p>It happens to all of us. You spend years in the trenches of systems administration, mastering the intricacies of BIND 9, manually tweaking MX records, and living inside getent and dig commands. Then, your career shifts. You move into orchestrating Kubernetes, managing IaC with Terraform, and focusing on cloud-native abstractions.&lt;/p>
&lt;p>Suddenly, you find yourself staring at a simple DNS issue, and it hits you: the muscle memory for the &amp;ldquo;basics&amp;rdquo; has started to fade.&lt;/p></description></item><item><title>Something I forgot ? Reclaiming the Fundamentals</title><link>http://halfknown.co.uk/stash/iloveit/</link><pubDate>Thu, 02 May 2024 08:58:59 +0000</pubDate><guid>http://halfknown.co.uk/stash/iloveit/</guid><description>&lt;h3 id="-------------if-youer-seeing-this--------">**** 🚧 IF YOU&amp;rsquo;ER SEEING THIS 🚧 ****&lt;/h3>
&lt;h4 id="---this-is-a-polite-notice-that-this-article-is-a-work-in-progress--">*** 🚦 THIS IS A POLITE NOTICE THAT THIS ARTICLE IS A WORK-IN-PROGRESS 🚥 ****&lt;/h4>
&lt;p>&lt;em>This article is currently being tweaked, drafted and is not yet complete. I’m sharing it early to document my process, so feel free to take a look at the current progress. I expect to finalize the content in my next commit&lt;/em>&lt;/p>
&lt;h4 id="thanks-for-reading-">THANKS FOR READING 🧐!&lt;/h4>
&lt;h4 id="do-enjoy-yourself-in-the-process-">DO ENJOY YOURSELF IN THE PROCESS 😇!&lt;/h4>
&lt;h1 id="heading">************&lt;/h1>
&lt;hr>
&lt;p>It happens to all of us. You spend years in the trenches of systems administration, mastering the intricacies of BIND 9, manually tweaking MX records, and living inside getent and dig commands. Then, your career shifts. You move into orchestrating Kubernetes, managing IaC with Terraform, and focusing on cloud-native abstractions.&lt;/p></description></item></channel></rss>