<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Francisco Pereira on Medium]]></title>
        <description><![CDATA[Stories by Francisco Pereira on Medium]]></description>
        <link>https://medium.com/@franciscopdevops?source=rss-1b24a3a83aab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*T8vsorHn9tQ6DrY-</url>
            <title>Stories by Francisco Pereira on Medium</title>
            <link>https://medium.com/@franciscopdevops?source=rss-1b24a3a83aab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:54:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@franciscopdevops/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I Deployed a Highly Scalable Application on Azure Kubernetes Service]]></title>
            <link>https://franciscopdevops.medium.com/how-i-deployed-a-highly-scalable-application-on-azure-kubernetes-service-56b8e8ea684e?source=rss-1b24a3a83aab------2</link>
            <guid isPermaLink="false">https://medium.com/p/56b8e8ea684e</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Francisco Pereira]]></dc:creator>
            <pubDate>Fri, 13 Sep 2024 12:08:55 GMT</pubDate>
            <atom:updated>2024-09-22T18:38:40.012Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Deployed a Highly Scalable App on Azure Kubernetes Service</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOnXmpmAoylCW3IM-tttRQ.png" /></figure><p>In this small project, an old-school infrastructure colleague suggested deploying the application on <strong>VMs managed by Vagrant.</strong></p><p>However, since the application could be containerized and <strong>the product owner requested an easily scalable architecture</strong>, I proposed a much more agile and straightforward solution: <strong>deploying the application on a Kubernetes cluster managed by the cloud provider (Microsoft Azure).</strong></p><p>This approach would free us from excessive configurations and underlying infrastructure management, such as VMs, <strong>allowing us to focus on continuous delivery, continuous integration, and application quality.</strong></p><p>Here is the solution and below what I’ve done:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPDXtIhx7Pfti7VJkf05Ug.png" /></figure><p>First step (<strong>using Azure CLI</strong>):</p><ul><li>Created a resource group and an <strong>Azure Container Registry.</strong></li><li><strong>Pushed the application’s Docker image</strong> to Azure Container Registry.</li><li>Created the cluster in <strong>Azure Kubernetes Service.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CgZfp_jb1-novAch5xuT5Q.png" /><figcaption>Azure Portal shows the Azure Kubernetes Service (AKS) created. CLI shows Docker images in Azure Container Registry (ACR).</figcaption></figure><p>Second step:</p><ul><li>Installed <strong>‘kubectl’ </strong>(interface that interacts with Kubernetes API).</li><li>Set permissions to log in to the Kubernetes cluster.</li><li>Attached Azure Container Registry to Azure Kubernetes Service.</li><li>Edited <strong>YAML files</strong> to include the correct Azure Container Registry image and to define resource and deployment aspects.</li></ul><p>Important: In YAML files, <strong>you declare the state and resources required for a cluster</strong>, including front-end pods, back-end pods, volumes, network policies, ports, services, ReplicaSets, and more. <strong>ReplicaSets, for example,</strong> <strong>help ensure high availability and horizontal scalability of applications.</strong></p><ul><li>And finally, <strong>I deployed the application to run in the Kubernetes cluster.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nACBrkdNMtL6JqJ27Rxw2A.png" /><figcaption>Azure Portal shows that the application’s front-end and back-end pods are running, as well as a Load Balancer with a public IP. The application can be accessed immediately!</figcaption></figure><p>Third and final step:</p><ul><li>Testing.</li><li>Validation.</li><li>Realize that <strong>a modern solution like Azure Kubernetes Service (AKS) simplifies container management</strong> by automating updates, integrating with other Azure tools, and providing <strong>auto-scaling and high availability.</strong> It also offers robust monitoring and diagnostics features.</li></ul><h4>A solution like this delivers built-in security, cost efficiency, and a quick setup for development and CI/CD pipelines, allowing teams to focus on strategic tasks and projects rather than heavy workloads.</h4><p><em>After this little project, my old school colleague changed his mind and is now a Kubernetes enthusiast.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56b8e8ea684e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>