|
🔗 Stories, Tutorials & Articles |
|
|
|
Who’s Calling That API? A Detective Story from the Depths of EKS Networking |
|
|
A production network got hammered by too many Auth0 token requests. The source? EKS workloads tucked behind a shared NAT Gateway. No easy trail.
Engineers stitched it together using VPC Flow Logs, pod-to-node maps, and some sharp Istio ServiceEntry logs. Even with Kubernetes CNI doing its NAT-obscuring thing, they pinned the blame on the exact pod. |
|
|
|
|
|
|
Most Cloud-Native Roles are Software Engineers |
|
|
Software Engineers still own the cloud-native job boards in 2025 - nearly 47% of all Kubernetes-tagged listings. DevOps holds onto second. But Platform Engineers just leapfrogged SREs, which have slid 30% since 2023. |
|
|
|
|
|
|
The Myths (and Costs) of Running Node.js on Kubernetes |
|
|
Kubernetes struggles to scale Node.js efficiently due to a mismatch in resource usage patterns. Autoscaling can be sluggish with bursty traffic, leading to revenue risks and performance issues. Teams must rethink resource allocation and scaling strategies to optimize Node.js efficiency in Kubernetes and avoid unnecessary costs and complexities. |
|
|
|
|
|
|
How I Built My Kubernetes Command Toolkit: A Journey from kubectl Chaos to Command Mastery |
|
|
A dev-built Kubernetes CLI framework reshapes kubectl for how teams actually work. Commands get grouped by role - dev, SRE, sec, admin - instead of by resource.
It bakes in defaults for Kyverno policies, encourages muscle-memory workflows, and wires up real-time troubleshooting to shrink downtime in prod. |
|
|
|
|
|
|
Kubernetes for agentic apps: A platform engineering perspective |
|
|
Agentic AI flips the old model. Instead of stateless, event-by-event workloads, we get stateful, self-steering systems that observe, reason, plan, and act - on loop.
Kubernetes steps up as the OS for this next phase. Boosted by platform engineering, it brings the right mix: ephemeral compute, persistent memory, tight orchestration, and a clean way to wire in tools.
Big picture: We’re moving from cloud-native microservices to something more alive - agent-native systems that think and adapt, not just react. |
|
|
|
|
|
|
Internal HTTPS Routing in Istio. |
|
|
Istio finally brings internal HTTPS routing with SNI-based traffic rules. Services in the mesh can now talk over port 443—TLS fully intact. Just like in prod.
TLS terminates at the ingress gateway. Routing pivots on SNI, not headers. Which makes this much closer to real-world mTLS flows.
What’s the play? Use internal HTTPS in your E2E tests. It closes the gap between test and prod, locking in tighter infra parity. |
|
|
|
|
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |