

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://www.cloudaddict.co.uk/</id>
  <title>Martin Lakov</title>
  <subtitle>A blog of all things Azure, DevOps, Containers and More.</subtitle>
  <updated>2024-10-25T03:05:50+00:00</updated>
  <author>
    <name>Martin Lakov</name>
    <uri>https://www.cloudaddict.co.uk/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://www.cloudaddict.co.uk/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://www.cloudaddict.co.uk/"/>
  <generator uri="https://jekyllrb.com/" version="4.3.4">Jekyll</generator>
  <rights> © 2024 Martin Lakov </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Azure Private DNS</title>
    <link href="https://www.cloudaddict.co.uk/posts/azure-private-dns/" rel="alternate" type="text/html" title="Azure Private DNS" />
    <published>2024-10-24T22:33:00+00:00</published>
  
    <updated>2024-10-24T22:33:00+00:00</updated>
  
    <id>https://www.cloudaddict.co.uk/posts/azure-private-dns/</id>
    <content src="https://www.cloudaddict.co.uk/posts/azure-private-dns/" />
    <author>
      <name>Martin Lakov</name>
    </author>

  
    
    <category term="azure" />
    
    <category term="dns" />
    
  

  
    <summary>
      





      Overview

DNS, DNS, DNS, It’s all about DNS. I’ve circled around this topic for a while, and it’s been a common discussion point with many of the clients I have worked with.

DNS is absolutely critical in any environment and if not done correctly it can cause a heap of issues. I am going to talk through some of the options for resolving DNS specifically for private endpoints in Azure and more i...
    </summary>
  

  </entry>

  
  <entry>
    <title>Running Azure Functions on Azure Container Apps</title>
    <link href="https://www.cloudaddict.co.uk/posts/running-azure-functions-on-azure-container-apps/" rel="alternate" type="text/html" title="Running Azure Functions on Azure Container Apps" />
    <published>2023-08-07T05:43:00+00:00</published>
  
    <updated>2023-08-07T05:43:00+00:00</updated>
  
    <id>https://www.cloudaddict.co.uk/posts/running-azure-functions-on-azure-container-apps/</id>
    <content src="https://www.cloudaddict.co.uk/posts/running-azure-functions-on-azure-container-apps/" />
    <author>
      <name>Martin Lakov</name>
    </author>

  
    
    <category term="serverless" />
    
    <category term="containers" />
    
  

  
    <summary>
      





      Service Overview

Microsoft recently announced the ability to run Azure Functions on Azure Container Apps (in preview). This is a big improvement over the current serverless option for Azure Functions as it allows us to leverage the benefits of microservices and the features of Azure Container Apps like DAPR and KEDA.

Behind the scenes, KEDA is used as the event driven auto scaler for the Func...
    </summary>
  

  </entry>

  
  <entry>
    <title>New Azure Service Retirement Workbook from Microsoft</title>
    <link href="https://www.cloudaddict.co.uk/posts/new-azure-service-retirement-workbook-from-microsoft/" rel="alternate" type="text/html" title="New Azure Service Retirement Workbook from Microsoft" />
    <published>2023-06-14T12:38:00+00:00</published>
  
    <updated>2023-06-14T12:38:00+00:00</updated>
  
    <id>https://www.cloudaddict.co.uk/posts/new-azure-service-retirement-workbook-from-microsoft/</id>
    <content src="https://www.cloudaddict.co.uk/posts/new-azure-service-retirement-workbook-from-microsoft/" />
    <author>
      <name>Martin Lakov</name>
    </author>

  
    
    <category term="monitoring" />
    
  

  
    <summary>
      





      Microsoft regularly releases new features and services in Azure. This is the evergreen nature of the cloud however they also retire services which is where infrastructure lifecycle management comes into play. Some new releases never make it out of preview and some services become legacy and get retired. A good example is a lot of the Azure classic services which were introduced when Azure was c...
    </summary>
  

  </entry>

  
  <entry>
    <title>Convert ARM Template to Bicep using VS Code Extension</title>
    <link href="https://www.cloudaddict.co.uk/posts/convert-arm-template-to-bicep-using-vs-code-extension/" rel="alternate" type="text/html" title="Convert ARM Template to Bicep using VS Code Extension" />
    <published>2023-04-11T23:47:00+00:00</published>
  
    <updated>2023-04-11T23:47:00+00:00</updated>
  
    <id>https://www.cloudaddict.co.uk/posts/convert-arm-template-to-bicep-using-vs-code-extension/</id>
    <content src="https://www.cloudaddict.co.uk/posts/convert-arm-template-to-bicep-using-vs-code-extension/" />
    <author>
      <name>Martin Lakov</name>
    </author>

  
    
    <category term="devops" />
    
  

  
    <summary>
      





      Introduction

Microsoft has just announced a new enhancement to their Bicep extension for Visual Studio code and I thought I would share this with the wider community.

Many of us have been working with ARM templates for a long time and it is evident that Microsoft is now pushing for Bicep adoption which is leaving a lot of engineers having to refactor existing ARM template deployments to Bicep...
    </summary>
  

  </entry>

  
  <entry>
    <title>Adding linting, validation and what-if to Bicep templates in Azure DevOps</title>
    <link href="https://www.cloudaddict.co.uk/posts/adding-linting-validation-and-what-if-to-bicep-templates-in-azure-devops/" rel="alternate" type="text/html" title="Adding linting, validation and what-if to Bicep templates in Azure DevOps" />
    <published>2023-02-26T22:17:00+00:00</published>
  
    <updated>2023-02-26T22:17:00+00:00</updated>
  
    <id>https://www.cloudaddict.co.uk/posts/adding-linting-validation-and-what-if-to-bicep-templates-in-azure-devops/</id>
    <content src="https://www.cloudaddict.co.uk/posts/adding-linting-validation-and-what-if-to-bicep-templates-in-azure-devops/" />
    <author>
      <name>Martin Lakov</name>
    </author>

  
    
    <category term="devops" />
    
  

  
    <summary>
      





      We are picking up from my last post where I walked through automating Bicep template deployments through Azure DevOps so if you haven’t caught up here is a link

The pipeline we set up in the previous post ran a single job that deployed our Azure resource using Bicep. However, in a production scenario we want to run some validation checks to ensure our new code won’t breaking anything. Stages i...
    </summary>
  

  </entry>

</feed>


