Kubernetes Basics: Exposing a Pod with Service and Ingress

This is a follow‑up tutorial to “Kubernetes Basics: Running Pods”. 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.

📋 Prerequisites

Before starting, ensure you have:

A running Kubernetes cluster (Minikube, Kind, EKS, GKE, AKS, etc.)
kubectl configured and working
The Nginx Pod from the previous tutorial running:
```
kubectl get pods nginx-pod
```

Daily DevOps learnings🧠

I’ve always been facinated with the wonders of DevOps and its various tools.

From version control in Git, to containerising applications with Docker, defining infrastructure as code using Terraform, automating configuration with Ansible, and orchestrating everything with Kubernetes. It’s awesome to see exactly how each tool fits into the bigger picture, turning manual processes into automated logic.

Recently, I find myself practising and demonstrating each tool, part hands-on with the help of AI ofcourse. Also enlightening myself, about different types of service mesh (istio or Linkered) or digging into different deployment strategies like rolling updates, blue‑green, and canary releases to understand how to ship changes safely and reliably.

Ive done a few, but would love to document the steps as a future reminder or also share with anyone who wishes to tag along Alt Text for accessibility

JayJay Ochinyabo | halfknown.co.uk

📋 JayJay's DevOps Diaries ..

Chronicling my journey through Cloud Native Infrastructure.. one step and tool at a time...

Kubernetes Basics: Exposing a Pod with Service and Ingress – Follow-up Tutorial

Kubernetes Basics: Exposing a Pod with Service and Ingress

📋 Prerequisites