<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>AKS on blog.ehn.nu</title><link>https://blog.ehn.nu/categories/aks/</link><description>Recent content in AKS on blog.ehn.nu</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Apr 2020 14:46:16 +0000</lastBuildDate><atom:link href="https://blog.ehn.nu/categories/aks/index.xml" rel="self" type="application/rss+xml"/><item><title>Implementing Azure Container Registry Retention with Brigade</title><link>https://blog.ehn.nu/2020/04/implementing-azure-container-registry-retention-with-brigade/</link><pubDate>Wed, 22 Apr 2020 14:46:16 +0000</pubDate><guid>https://blog.ehn.nu/2020/04/implementing-azure-container-registry-retention-with-brigade/</guid><description>&lt;p&gt;If you are doing any work related to containers and Azure, you are most likely using &lt;a href="https://azure.microsoft.com/en-us/services/container-registry/"&gt;Azure Container Registry&lt;/a&gt; for storing images. The amoun of storage available for these images depends on the pricing tier you are using.&lt;br&gt;
If you exceed this amount of storage, you will pay an additional fee for every GB of image data that exceeds the limit. See the table below for the current pricing details.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Azure Container Registry pricing details&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Event-driven scripting in Kubernetes with Brigade</title><link>https://blog.ehn.nu/2020/01/event-driven-scripting-in-kubernetes-with-brigade/</link><pubDate>Sun, 19 Jan 2020 10:59:22 +0000</pubDate><guid>https://blog.ehn.nu/2020/01/event-driven-scripting-in-kubernetes-with-brigade/</guid><description>&lt;p&gt;In most projects that I’ve been part of, sooner or later the need for various types of automation jobs arises. For example cleaning up old files, moving database backups, running health checks or system tests and so on.&lt;/p&gt;
&lt;p&gt;Historically we’ve implemented these tasks using for example the Windows task scheduler, or through some custom Windows Service app. More recently, we’ve been using Azure Automation jobs for this. Sometimes it can also make sense to use CI/CD automation tools like Azure DevOps for these jobs.&lt;/p&gt;</description></item><item><title>Getting started with Windows Containers in Azure Kubernetes Service</title><link>https://blog.ehn.nu/2019/06/getting-started-with-windows-containers-in-azure-kubernetes-service/</link><pubDate>Fri, 28 Jun 2019 14:12:04 +0000</pubDate><guid>https://blog.ehn.nu/2019/06/getting-started-with-windows-containers-in-azure-kubernetes-service/</guid><description>&lt;p&gt;Many of us have eagerly been waiting for the announcement that Microsoft made at the Build 2019 conference, Windows Containers is now in public preview in Azure Kubernetes Service! Yes, it’s in preview so we still have to wait before putting applications into production but it is definitely time to start planning and testing migrations of your Windows applications to AKS, such as full .NET Framework apps.&lt;/p&gt;
&lt;p&gt;Containers on Windows are still not as mature as on Linux of course, but they are fully supported on Windows and it is now GA on Kubernetes since version 1.14.&lt;/p&gt;</description></item></channel></rss>