<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AKS on iAutomate</title>
    <link>/tags/aks/</link>
    <description>Recent content in AKS on iAutomate</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 02 Nov 2021 00:00:00 +0000</lastBuildDate><atom:link href="/tags/aks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating a simple deployment in Azure Kubernetes Service using YAML (Less than 5 min)</title>
      <link>/blog/creating-a-simple-deployment-in-azure-kubernetes-service-using-yaml-less-than-5-min/</link>
      <pubDate>Tue, 02 Nov 2021 00:00:00 +0000</pubDate>
      
      <guid>/blog/creating-a-simple-deployment-in-azure-kubernetes-service-using-yaml-less-than-5-min/</guid>
      <description>Introduction In my previous blog posts, we have seen imperative approaches for creating pods, deployments, replica sets and exposing them to load balancer service. The links below are for your reference.
 DEPLOY NGINX APPLICATION IN AKS (LESS THAN 5 MIN) DEPLOY A NEW VERSION OF THE APPLICATION IN AKS (LESS THAN 5 MIN) DRY RUN OF REPLICAS IN AZURE KUBERNETES SERVICE (LESS THAN 5 MINUTES)  YAML Basics YAML is a human-readable data serialization language used for configurations and many other purposes.</description>
    </item>
    
    <item>
      <title>Dry run of Replicas in Azure Kubernetes Service (less than 5 minutes)</title>
      <link>/blog/dry-run-of-replicas-in-azure-kubernetes-service-less-than-5-minutes/</link>
      <pubDate>Sun, 24 Oct 2021 00:00:00 +0000</pubDate>
      
      <guid>/blog/dry-run-of-replicas-in-azure-kubernetes-service-less-than-5-minutes/</guid>
      <description>Introduction Below two blog posts are to demonstrate creating Pod &amp;amp; Deployment imperatively.
1.	Creating Pods
2.	Updating the application to a newer version.
 Disclaimer: This post is to show scaling the application (With no YAML) &amp;amp; not recommended for production.
 In this post let me walk through the simple steps for creating replicas. In simple words, replicas are nothing but a copy of the pods running to maintain the availability of an application.</description>
    </item>
    
    <item>
      <title>Deploy a new version of the application in AKS (Less than 5 min)</title>
      <link>/blog/deploy-a-new-version-of-the-application-in-aks-less-than-5-min/</link>
      <pubDate>Thu, 21 Oct 2021 00:00:00 +0000</pubDate>
      
      <guid>/blog/deploy-a-new-version-of-the-application-in-aks-less-than-5-min/</guid>
      <description>Introduction In my previous blog, we described the pod deployment and exposing the app to the internet. Now, let me walk through the steps to release a new version of the application. We have two application versions in the Docker repository and they are listed below
 Version 1 Version 2    Steps (High Level)  Build an HTML static web application – Content is of your choice Dockerize the application Tag and publish to the Docker hub Deploy the containerized application in the AKS Release a newer version of the application in the AKS  HTML Code &amp;amp; Dockerfile Content &amp;lt;!</description>
    </item>
    
    <item>
      <title>Deploy NGINX application in AKS (Less than 5 min)</title>
      <link>/blog/deploy-nginx-application-in-aks-in-5-min/</link>
      <pubDate>Thu, 21 Oct 2021 00:00:00 +0000</pubDate>
      
      <guid>/blog/deploy-nginx-application-in-aks-in-5-min/</guid>
      <description>Introduction Of late, we did a AKS workshop and a team got stuck in deploying a simple HTML application and get the home page working. It’s not a complex one! Let me walk through the steps to get this sorted.
Project Structure &amp;amp; Code HTML application project folder structure
The docker file content is as follows - Yes, team has a HTML file named &amp;lsquo;home.html&amp;rsquo;
FROMnginxCOPY home.html /usr/share/nginx/htmlHTML file content for your reference.</description>
    </item>
    
  </channel>
</rss>
