Wolkwacht topic
Patterns for building cloud platforms that teams can operate, govern and evolve.
Platform engineering is the work of turning architectural intent into dependable paths for delivery and operations. This collection focuses on useful abstractions, GitOps, governance and the decisions behind sustainable cloud platforms.
Recommended entry point
A concrete example of turning platform intent into a repeatable operating model.
Selected reading
The Unseen Work of a Cloud Architect: A Story About Building Azure the Hard (and Right) Way The story of implementing an Azure cloud environment rarely starts with technology. It …
Inside Microsoft’s New AKS Desktop
Kubernetes is very good at reporting desired state. A Deployment can be available while its pods restart every few hours. A cluster can show green nodes while workloads have no …
Kubernetes has become so familiar that many teams don’t choose to adopt it anymore; they just start using it. When a new internal API appears, someone sets up an AKS …
Follow the thread
Governance and operating patterns for platforms that have grown beyond one cluster.
Automatically updated
Transferring a Dapr-enabled application from local Kubernetes to AKS should be straightforward. The annotations, app ID, application port, sidecar API, and workload manifest stay …
To quickly grasp Dapr on Kubernetes, it’s best to start locally rather than with an AKS cluster. Local setup allows for rapid pod creation in seconds, minimizes the consequences …
Every distributed application gathers various plumbing components. One service requires retries and timeouts, another needs a message broker client, and a third must store some …
The real question is not whether to use the Azure Key Vault provider for the Secrets Store CSI Driver or the External Secrets Operator (ESO). Instead, it’s whether your …
Kubernetes is very good at reporting desired state. A Deployment can be available while its pods restart every few hours. A cluster can show green nodes while workloads have no …
Kubernetes has become so familiar that many teams don’t choose to adopt it anymore; they just start using it. When a new internal API appears, someone sets up an AKS …