GitOps on Azure Kubernetes Service: Building a Production-Ready Platform with Flux
Kubernetes platforms seldom fail due to the technology itself; instead, failures are usually caused by operational issues.
Wolkwacht topic
Practical guidance for designing, securing and operating Azure Kubernetes Service.
AKS removes control-plane management, but production platforms still require deliberate decisions about identity, networking, reliability, cost and day-two operations. This topic collects field-tested guidance for making those decisions.
Recommended entry point
A complete, opinionated path from cluster foundations to workload and runtime security.
Selected reading
Kubernetes platforms seldom fail due to the technology itself; instead, failures are usually caused by operational issues.
Introduction: Cost Is an Outcome of Scheduling Decisions
Most teams begin their AI journey by using a managed model API. This approach works initially but can become problematic when costs become…
There’s a moment in every Kubernetes journey when the cluster begins to feel… heavy. Not broken, not misconfigured, but stretched in ways…
Follow the thread
Networking, observability, scaling, governance and the multi-cluster reality.
From AppNet fundamentals to zero-trust, multi-cluster and AI gateway patterns.
Automatically updated
Ingress-NGINX has stopped receiving patches, so it's time to plan the move. Here's what I would look at, whether you run AKS or managed Kubernetes at a hosting provider, plus what I learned testing the migration paths.
Production readiness starts where most tutorials end. Installing Dapr, deploying sidecars, and proving the building blocks are necessary milestones, but they do not answer the …
A Dapr-enabled application can work perfectly with one replica and still be unprepared for production. The sidecar may have no resource requests, every application may be able to …
A request can fail even when every Kubernetes pod is Running. The application may be waiting for a Dapr component, a retry may mask a slow dependency, or a call may reach the …
The first six parts of this series covered Dapr’s most familiar building blocks: service invocation, state management, and pub/sub. They solve application-to-application …
A synchronous request establishes a direct dependency: the caller pauses while the destination handles the task. This approach is suitable when an immediate response is required. …