Tag: Kubernetes
-
Apply configuration changes to the default node pool in AKS via Bicep
In today’s blog post we look into the Bicep and how to apply configuration changes to the default node pool in Azure Kubernetes Service within the same Bicep template. What sounds easy on the first look gets nasty if all the things shall be done within the same template like creating an Azure Kubernetes Service…
-
How to change the node size of the default node pool in AKS without downtime?
Currently, as of writing this blog post, Azure Kubernetes Service does not support changing the node size of the default node pool or additional node pools without recreating the whole AKS cluster or the additional node pool. Having all the configuration in infrastructure as code whether it is Bicep or Terraform seems to be a…
-
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…