Category: Azure
-
Conditions with for_each in Terraform
Conditions in Terraform are well-known and can provide in combination with the for_each argument a lot of flexibility. In today’s blog post I walk you through an example storage module I have created to showcase the topic. The module consists of three resources a resource group, a lock, and a storage account. As I am…
-
Kubernetes CPU requests demystified
Two weeks back I participated in an incredibly good and vivid discussion on Twitter about Kubernetes CPU requests and limits. During the discussion I learned a lot and were proven that my knowledge and statement are not correct. I had made the following statement: “CPU requests are used for scheduling but are not guaranteed at…
-
Using Rancher Desktop as Docker Desktop replacement on macOS
Last year I wrote a blog post about running Podman on macOS with Multipass as a Docker Desktop replacement. -> https://www.danielstechblog.io/running-podman-on-macos-with-multipass/ Back at that time I had looked also into Podman Machine and Rancher Desktop. Podman Machine was out very quickly without support for host volume mounts. Rancher Desktop instead was promising but the host…
-
Remove dangling multi-arch container manifests from Azure Container Registry
Last year I wrote a blog post about removing dangling container manifests from ACR. -> https://www.danielstechblog.io/remove-dangling-container-manifests-from-azure-container-registry/ I did not cover an edge case when it comes to multi-arch container manifests. So, here we are, and I walk you through that topic today. First, do not be afraid the PowerShell script from last year works perfectly…
-
Running gVisor on Azure Kubernetes Service for sandboxing containers
gVisor is one option beside Kata Containers or Firecracker for sandboxing containers to minimize the risk when running untrusted workloads on Kubernetes. -> https://gvisor.dev/ Currently, the only managed Kubernetes service which supports gVisor in dedicated node pools per default is Google Kubernetes Engine. But with a bit of an effort this is doable as well…
-
Run the Istio ingress gateway with TLS termination and TLS passthrough
The Istio ingress gateway supports two modes for dealing with TLS traffic: TLS termination and TLS passthrough. Running Istio with TLS termination is the default and standard configuration for most installations. Incoming TLS traffic is terminated at the Istio ingress gateway level and then sent to the destination service encrypted via mTLS within the service…